Format model inputs in p2a_model.R#169
Conversation
galengorski
left a comment
There was a problem hiding this comment.
Hi @lekoenig this looks good to me! I'm wondering if there is a way that we can map the snakemake dependencies per your comments on lines 171-174, I always find it confusing to track down which of the snakefile need changing, but maybe that is just the nature of a complex pipeline.
I agree and would love to incorporate any suggestions for taking the burden of tracking dependencies out of our heads and into comments and code! Do you have an example of what you mean by mapping the snakemake dependencies? Are you referring to added documentation somewhere? |
|
My thought (hope?) was to treat the So now we include the model configuration options in I suggest we think about this further and make additional changes when we tackle #146. I'll go ahead and merge this PR for now. |
This PR addresses part of #159, namely that there were redundant COMID columns in the
inputs_and_outputsdata frame inp2a_well_obs(e.g.COMID.x,COMID.y). Here I've addedCOMIDas a join key when buildingp2a_well_obsto omit the redundant columns.I've also added some comments and made formatting edits in both
2a_model.Rand2a_model/src/model_ready_data_utils.Rto 1) add documentation that will allow us/me to better track the different steps in2a_model.R; and 2) format some function documentation to match the code style used throughout the rest of the repo.