Eric Bruning

Hi @cnairy, the import error ("no module") might be because you haven't activated the conda environment (usually `global`) into which you installed `glmtools`. Regarding the overall data flow, have you...

@hopesea79 Thanks for your contribution to help get this branch ready for use in ISatSS. I think this summarizes your changes: 1. You propose to use the value of `fill`...

@djhoese thanks for calling my attention to that outstanding issue. I commented over there to indicate that I think it's a good idea. I think 2. above is an additional...

I'm not picky about whether it's one argument or two … let's follow the wisdom of any available Unix conventions. This also relates to #26 - how do we expose...

@hopesea79 I renamed this PR just now to reflect that it is a discussion about how to take the ugf-newgrid branch meant for standalone use and adapt it to ISatSS....

See #63 for changes to the default output path for #54. @hopesea79 This will impact ISatSS integration, but should be a very simple change. Instead of running `make_GLM_grids.py` with `-o...

I just merged ugf-newgrid into master, and created a new isatss-ugf-newgrid branch for use in making any remaining changes that are desired for integration into ISatSS. I suggest migrating these...

`make_GLM_grids.py` is the expected entry point for most users, since it handles configuration of the call to `grid_GLM_flashes`. So I want it to be useful for all ordinary use cases....

@djhoese let's go for the route you proposed above. If there's a way to retain backwards compatibility with a default, for instance to `-o`, let's do that, but I'm not...

@djhoese are you still thinking of pushing any of the changes above? In #59 you mentioned you were going to take a look at it in the fleeting moments before...