Message boards :
Number crunching :
APP names for use in app_config?
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 30 Apr 13 Posts: 106 Credit: 3,805,237,860 RAC: 65 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
This question may be premature for the system updates in progress, but I'm getting error msgs re: my app-config which used to be fine. (I'm running Einstein only now, but when I reboot my PC and restart BOINC it reloads the idle GPUGRID app_config and throws errors.) What are the correct APP names to use in app_config, e.g. <name>ATMML</name> <name>PythonGPU</name> <name>acemd3</name> for all apps: ATM, ATMML, ACEMD3 (<--those used to work but throw errors now), and Quantum Chemistry? Thanks! |
|
Send message Joined: 21 Feb 20 Posts: 1116 Credit: 40,839,470,595 RAC: 6,423 Level ![]() Scientific publications
|
This question may be premature for the system updates in progress, but I'm getting error msgs re: my app-config which used to be fine. Since the project is "new" to the BOINC client (the URL change makes it appear as a completely new project). BOINC is designed to recognize app names based on the host's history or receiving work. if you havent received work for these projects since adding the new URL, then BOINC isnt aware of them and will complain about it. the app names should be the same as before. ATM ATMML acemd3 PYSCFbeta I would go ahead and remove the PythonGPU one. I dont think those kinds of tasks will come back.
|
|
Send message Joined: 11 Jul 09 Posts: 1639 Credit: 10,159,968,649 RAC: 428 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
I imagine that the app_names will be unchanged when this is over. You're seeing these messages because the master file name for the project has been changed. That's a critically important change for the project, though I suspect the current admin team didn't realise quite how critical. Changing the master file name in effect changes the whole identity of the project - it turns it into a whole new project. And BOINC responds by 'resetting' the project - deleting all files related to the old identity, and downloading a new set (once available). Once you are allocated work from the new server, it should auto-recognise the old names in app_config, and use your settings as before. |
|
Send message Joined: 30 Apr 13 Posts: 106 Credit: 3,805,237,860 RAC: 65 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Thanks. I've tried to get new work but only "got 0 new tasks" since the updates. Is it odd that the event log also doesn't say "no tasks available"? I see tasks available in Server State, but it's been stuck at those numbers for days. |
|
Send message Joined: 30 Apr 13 Posts: 106 Credit: 3,805,237,860 RAC: 65 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Thanks. I've tried to get new work but only "got 0 new tasks" since the updates. Is it odd that the event log also doesn't say "no tasks available"? I see tasks available in Server State, but it's been stuck at those numbers for days. |
|
Send message Joined: 21 Feb 20 Posts: 1116 Credit: 40,839,470,595 RAC: 6,423 Level ![]() Scientific publications
|
Thanks. I've tried to get new work but only "got 0 new tasks" since the updates. Is it odd that the event log also doesn't say "no tasks available"? I see tasks available in Server State, but it's been stuck at those numbers for days. see explanation here: https://gpugrid.net/gpugrid/forum_thread.php?id=5409&postid=62242#62242
|
©2025 Universitat Pompeu Fabra