PR313 follow-up: proposed config and arguments format

[israelmcmc]

Same functionality as #313, but I'm changing the config file and argparse arguments with a proposed general format.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.45%. Comparing base (eb587a9) to head (83e4e83).

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ldigesu]

Hello Israel, I started testing this. Let me know how we proceed. Will you implement the comments and then merge in my branch, or the other way around?

In any case, for now, I noticed the following:
i) The override option does not work for me. Likely, it's me doing something wrong. E.G.The command cosi-threemlfit --config ./my_config --override “sc_file:./sc.ori” results in this error: config.override(*args.override)
File "/Users/lauradigesu/opt/anaconda3/lib/python3.9/site-packages/yayc/configurator.py", line 124, in override
key,value = args[0].split("=")
ValueError: not enough values to unpack (expected 2, got 1)

ii) I tested the time cuts, and they work for me. However, all the functions that are called there need numerical values as input, not a Time object. Thus, I made everything work by adding tstart.value/tstop.value anywhere in lines 103-108 of task.py. My working example is grb of 88s of dc3, however I'll think about how an example for this using the internal test_data of cosipy.

iii) maybe it would be useful to add the option of adding a user-defined prefix or suffix to the names of the outputs? Since everything does not get overwritten by default, maybe one wants to keep track of which source is being fitted directly in the names of the output files.

Cheers,