CANFLUX / Calculation_Procedures

Ini files for cleaning under ../Database/Calculation_Procedures
0 stars 1 forks source link

Default Configurations: where to save non-Site specific settings #96

Open June-Skeeter opened 7 months ago

June-Skeeter commented 7 months ago

@sknox01, @znesic

In the lab meeting last week, it was mentioned that ideally, each project would have a separate copy/fork of Calculation_Procedures. This brings up the question of how best to handle default configuration settings that are common among all sites, that we don't want to diverge, like the new _config.yml file, which defines the new third stage procedures (and can be extended to define any number of other defaults). It might be more appropriate for these to be stored closer to the code which is running them (e.g., in Biomet.Net).

Alternatively/additionally, it might be a good idea to create a Fork of Biomet.Net, and parse it down so that it only contains code that is relevant to the "Calculation_Procedures" pipeline, and put them in this repo or some new repo? That would help prevent changes to the pipeline moving forward from breaking anything that currently has running elsewhere. Forks are similar to branches, but are a better option when we don't intend to re-incorporate changes down the line

Just some food for thought.