Write an RRnom tools file
Move functions and write an RRnom tools file. This is what will be used to generate the external data products for use by PE tools like BILBY.
Jeff writes:
RRnom is an "interesting case study" for a large clunky hunk of code that spans the scope of both pyDARM and data analysis. We should consider, among many things:
- What functionality within RRnom can be stripped out and replaced with pyDARM functions
- What functionality is unique to RRnom, but would be better suited as a module in pyDARM
- Whether RRnom itself should be a pyDARM module, or if it should be its own "project", and/or
- How does pyDARM interact with modules / projects / scripts / data in general given GIT's insistence that everything is a siloed thing independent of everything else.
RRNom should be written in such a way that it may me packaged and imported to be used in a functional form within other python scripts. Namely, I need to be able to call it repeatedly, and not have to load in a text file from some other random directory to get the results of that call.
Evan adds:
The whole RRNom program needs a significant cleanup. There have been a number of run or epoch specific issues that are addressed with a multitude of if-else statements. The logic is perhaps not always consistent throughout the program. I’m unsure how best to clean that up since every special case needs some kind of logic to do something different than the standard case.