Chris Markiewicz
Chris Markiewicz
@a3sha2 I'm going to try to make a release in the next couple days. If you want to try to finish this off, I'd love to include it!
> > My only hesitance is the potentially misleading runtime_threads ― maybe that should be fixed before restoring this functionality? > > I agree Was this fixed? What needs doing?
Yeah, seems like we want something like: ``` if status_dict['runtime_threads'] != "N/A": status_dict['runtime_threads'] //= 100 ```
This is most likely a memory error. How much memory and how many CPU cores are available to the process?
Would 24gb be possible? AROMA is a memory hog.
You can try 16GB, and setting --n-cpus 1. That will keep multiple processes from competing for limited memory. If you reuse the working directory, then it should start at AROMA.
Yes, though you can also kill the job after AROMA is done and resume with more cores.
I'm pretty sure it is... it shows up in the reports and @markushs reported we were double-applying.
@Lestropie I really hoped to be able to get to this during July, but failed. I'm now going to be out for three weeks for vacation and a dedicated sprint...
Alternately, we could also add confounds to `--ignore`...