Posts by MJH333

1) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 109091)
Posted 20 days ago by MJH333
Post:
[Duplicate post deleted]
2) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 109090)
Posted 20 days ago by MJH333
Post:
Looking like they're still fed up with me... no response & no change I can notice
Thank you for trying.

The Server Status info on the Rosetta home page has not updated since 4 Apr 2024, 11:03:04 UTC. I hope this will start updating again once the validator is fixed.
3) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 109034)
Posted 25 Mar 2024 by MJH333
Post:
I'm not sure what is going on but about 1/4 of the work units are reporting "Error while computing" and I am no longer getting new tasks (which I assume is due to the errors).
I doubt that there is anything wrong with your system. The latest big batch of work units has run out.

You can see this from the Server Status section on the Rosetta home page: https://boinc.bakerlab.org/rosetta/, which currently shows "Total queued jobs" of 0. It can also be seen from the Project status page: https://boinc.bakerlab.org/rosetta/server_status.php, which currently shows "Tasks ready to send" of 0.

You may, of course, pick up the odd resend, or some Robetta tasks, but there will be no steady flow of tasks until another big batch of work units is released.

We may get another batch if/when the work units you identified with the "residue 1 does not have a LOWER_CONNECT" error are corrected and reissued.

When trying to get an idea of how much work is available, I tend to look at the "Total queued jobs" figure on the Rosetta home page because that shows all the work units available to be crunched, which may be in the millions. Whereas the "Tasks ready to send" figure on the Project status page shows just the tasks ready to be distributed, which is usually no more than 5,000.
4) Message boards : Number crunching : Help with VirtualBox (Message 108825)
Posted 1 Feb 2024 by MJH333
Post:
Have a look at https://boinc.bakerlab.org/rosetta/forum_thread.php?id=14903
5) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 108744)
Posted 5 Dec 2023 by MJH333
Post:
Does anyone know whether these Rosetta beta tasks run better in Windows or Linux?

I ask because I recently discovered that WCG Smash Childhood Cancer tasks run much faster in Linux than Windows.

I'm currently running the Rosetta beta tasks in Windows, but could switch to Linux if there is a significant advantage in doing so.
6) Message boards : Number crunching : Rosetta Beta 6.00 (Message 108304)
Posted 14 Apr 2023 by MJH333
Post:
Lots of crashes on my Ryzen 7 5800X. None received on my i5-9600K so I can't tell if it's just that machine of mine or if it's a general thing
My Ryzen 9 5950X got 6 beta tasks, all completed and validated OK.
7) Message boards : Number crunching : Opting out of rosetta python projects? (Message 106280)
Posted 26 May 2022 by MJH333
Post:
Don’t amend the app_config.xml file.

Just go to your account page on the Rosetta website, then click to view Computers on this account, then Click Details for your computer, then go to the bottom where it says VirtualBox VM jobs and click Skip.

Do that for each computer attached to Rosetta, and you won’t get Python tasks.
8) Message boards : Number crunching : Not getting work (Message 105712)
Posted 26 Mar 2022 by MJH333
Post:
I've verified that "allow" is selected for my one computer

Anyone have any suggestions?
If the Allow switch is showing, then your PC is set not to receive Vbox tasks. You need to click it to allow Vbox tasks. It will then change to Skip (and if you click that, you will stop getting Vbox tasks).

It appears that, if one of the Python tasks errors out, the system automatically turns off Python tasks on the computer that had the error.
9) Message boards : News : Thank you! (Message 105621)
Posted 21 Mar 2022 by MJH333
Post:
Go to your account homepage on the Rosetta website, click on "View" next to "Computers on this account", then click on "Details".

At the bottom, there is a toggle switch headed "VirtualBox VM jobs". If it says "Allow", click it, and you will start getting Pythons once your Boinc Manager communicates with the server.

If you click "Allow" and then "Return to host page", you will see that the toggle now says "Skip" (and clicking it would then stop you getting Pythons).
10) Message boards : Number crunching : Not getting work (Message 105346)
Posted 6 Mar 2022 by MJH333
Post:
Thanks, Doug, glad to be able to help.

This has happened to me several times now, so I've had a fair bit of practice at clicking the "Allow" switch!

Cheers,
Mark
11) Message boards : Number crunching : Not getting work (Message 105344)
Posted 6 Mar 2022 by MJH333
Post:
Doug,

It sounds to me as if one of the Pythons running on your machine has errored out. This causes the server to stop sending you Python tasks. (And there are currently no Rosetta 4.20 tasks available, so you are not getting any tasks at all.)

To check, go to your Rosetta account homepage, click on "View" next to "Computers on this account", then click on "Details".

At the bottom, there is a toggle switch headed "VirtualBox VM jobs". If it says "Allow", click it, and you will start getting Pythons again once your Boinc Manager communicates with the server.

If you click "Allow" and then "Return to host page", you will see that the toggle now says "Skip" (and clicking it would then stop you getting Pythons).

If the toggle switch says "Skip" when you look at it, then there is something else afoot!

Cheers,
Mark
12) Message boards : Number crunching : There's a max WU of 8 with Virtualbox (Message 104867)
Posted 17 Feb 2022 by MJH333
Post:
It’s a lack of RAM.


There are no complaints in the event logs regarding ram.

Dougga,

I have two 4C/4T laptops running Pythons. With 8GB of RAM, they would run only 2 tasks at a time. I increased the memory on both to 16GB, and they both now run 4 Pythons.

The fact that your machine has 32GB of RAM and can run only 8 Pythons is what led me to think that RAM is the issue. But as Grant (SSSF) has pointed out, disk space can also be a problem with the Pythons.

I have to confess that I couldn’t remember what the Event Logs said about this issue when I only had 8GB of RAM. So I conducted a little experiment this morning, taking 8GB out of one of the laptops.

Doing this caused 2 of the 4 Pythons to stop running, with the message “Waiting for memory” showing in the Status section of Boinc Manager for the tasks. Aborting one and downloading another caused the Status message for the new one to read “Ready to start” instead of “Waiting for memory”. So the message for tasks which haven’t yet started because of lack of RAM seems to be simply “Ready to start”.

I also looked at the Event Log. It did not mention the fact that tasks weren’t running because of a lack of memory. I think I have the default options for the Event Log.

Changing those options by using Options>Event Log options in Boinc Manager to add in mem_usage_debug resulted in the Event Log recording that those 2 Pythons “can’t run, too big”.

I thought I would record this, in case you or others find it helpful.

Cheers,
Mark
13) Message boards : Number crunching : There's a max WU of 8 with Virtualbox (Message 104835)
Posted 16 Feb 2022 by MJH333
Post:
It’s a lack of RAM.

See Falconet’s post (Feb 11 at 5:16pm) on the World Community Grid forum here https://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,44037_offset,0
14) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103825)
Posted 14 Dec 2021 by MJH333
Post:
I wonder if anyone could help me with something that has been puzzling me.

I have two 4C/4T Intel laptops running RAH. When the 4.20 tasks ran out recently I tried running Pythons on them on Linux without much success.

I then adopted the suggestion from Jim1348 of switching to Windows and trying VirtualBox 5.2.44, which worked (thank you!).

The only problem then was that I could only run 2 tasks at a time instead of 4. So I bought some more memory for one of the laptops, doubling it from 8GB to 16GB. But that laptop would still only run 3 tasks at a time.

Does anyone have any idea why that would be? I had assumed that, if I can run 2 tasks on 8GB, I would certainly be able to run 4 tasks on 16GB. But that assumption appears to have been wrong.

For the moment, I've switched back to 4.20 only, in order to use all the cores. But if anyone has any ideas as to why I can't run 4 Pythons at a time, or otherwise as to how to troubleshoot this issue, I would be very grateful.

I'm happy to buy more memory for the other laptop as well, but it seems a bit of a waste of money just to run 3 Pythons instead of 2.

Cheers,
Mark
15) Message boards : Number crunching : Excessive workunit fetch (Message 103172)
Posted 11 Nov 2021 by MJH333
Post:
I never got such a problem on any other project

I’ve had this problem several times on World Community Grid. I’ve stopped using max_concurrent on WCG because of this.
16) Message boards : Number crunching : Rosetta needs 6675.72 MB RAM: is the restriction really needed? (Message 101811)
Posted 15 May 2021 by MJH333
Post:
When it happens to me on my laptop, I set No New Tasks, suspend all unstarted tasks, then as each running task ends, more RAM becomes available. At the point there's enough for the problem task to start, I then unsuspend one task at a time, then find all my cores can run again.

I know it's a faff, but it's the only way I've found to get around it.


Sid and Grant,

Thank you for your further thoughts on this. I find it puzzling, as yesterday I had 4 of these pre-helical-bundle tasks running at the same time on the laptop whereas the day before it could only manage 3. But anyway, next time it happens I will try Sid’s suggestion for unclogging the bottleneck - thanks for that.

Mark
17) Message boards : Number crunching : Rosetta needs 6675.72 MB RAM: is the restriction really needed? (Message 101799)
Posted 12 May 2021 by MJH333
Post:
Nope, the problem is that there is a (extremely large) batch of work that was incorrectly configured for it's minimum RAM & Disk requirements.
Unless you've actually got enough RAM that is free that meets those requirements, then BOINC won't let one of those Tasks run until the RAM/Disk available requirements are met (even though the actual usage values are only a fraction of the required values). Same for the disk space requirements.

If you set your BOINC Manager to Advanced view & look at Tools, Event log, you should see some messages there relating to how much RAM you have, and how much RAM BOINC thinks it will need in order to run the Task when it tries to get more work, or start the paused Task.


Thank you, that's really helpful.

Mark
18) Message boards : Number crunching : Rosetta needs 6675.72 MB RAM: is the restriction really needed? (Message 101797)
Posted 12 May 2021 by MJH333
Post:
Hi Grant
May I ask you a quick question about this?
My 4 core laptop (no SMT) is attempting to run 4 pre_helical_bundles tasks, but one is shown as "Waiting for memory". I have set RAM usage to 95% in Computing preferences (whether or not in use) and the system monitor (in Linux Mint) shows that I am using only 2.6GiB of 7.6GiB (34.3%) memory. So I am puzzled as to why the 4th task is not running. The system monitor also says "Cache 4.6GiB". Is that counting against the 95% limit? I tried a 99% limit but that made no difference.
Any thoughts you have on this would be much appreciated. I'm a newbie cruncher, so I'm probably doing something wrong!

Mark






©2024 University of Washington
https://www.bakerlab.org