Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Restart Pecan on Emu with Geoduck files #526
@seanb80 please run the following 4 sample files in the following order:
Geoduck1 (corresponds to Geoduck 48 @ Site Fidalgo Bay = Eelgrass)
When these are done I'll have another set to run.
Chatted with Sean to sketch out this next Pecan run timeline.
If we use 4 of the 16 logical cores on Emu (we used 3 in the recent test run, and tried 14 in the big run that didn't work / was cancelled), using the 80 isolation windows: it should take ~13.5 days to complete 2 data files (aka 2 samples).
This is assuming that only using 3 isolation windows and 3 logical cores = 10 hours per sample file, and that increasing the logical cores from 3 to 4 results in a linear decrease in time/isolation window.
Bottom line, with the given settings I should have data from 1 sample file done in a week, which I'll plan on using for the poster.
It looks like Pecan/Grid Engine is still using much more memory than I gave it permission to, but hopefully with fewer processes running this won't end poorly. Will monitor it over the weekend to make sure it's behaving properly.
The Res is the closest approximation to memory used by a process, and it looks like our four python instances are using 0.016 terabytes (16gb), 0.015 terabytes (15gb), 7.6gb and 6.7gb respectively.