-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nf chunking #469
Nf chunking #469
Conversation
Nf chunking
Hello @rachelelim! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:
|
is this a dupicate PR to #461 @rachelelim ? |
scripts/process_nf.py
Outdated
@@ -127,6 +126,8 @@ | |||
beam_stop_parms=np.array([beam_stop_y_cen,beam_stop_width]) | |||
|
|||
|
|||
max_RAM = 256 #max amount of memory to available in GB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this hardcoded value? Don't like it, as it is generally bad practice. Python has utils for finding available memory:
import psutil
mem_info = psutil.virtual_memory()
# to get available memory in bytes, do:
# mem_info.available
scripts/process_nf.py
Outdated
# %% NEAR FIELD - splitting | ||
#============================================================================== | ||
|
||
max_RAM = 1 # in GB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See above. Not good to hardcode things when you can ask the system for available memory. Available means not having to use disk.
your tasks to merge this:
|
Gonna make one comment: In places where you have placeholder strings, start thinking about a YAML config that specifies the required variables. |
Fixed chunking with no leftovers