Conversation
|
At this stage The temporary solution is to comment a whole section in F2_autoreport but that just deletes log messages from the all reports. |
|
@Bachibouzouk @TheOneAndra is this something that should be merged in the near future? If so, @TheOneAndra can you do a local rebase and force push (in coordination with @Bachibouzouk)? |
This PR was made on request from PF so that he can have a trace of my local changes we made. I don't think this PR will be merged as is, but just used by PF at some point, maybe @Bachibouzouk you have another opinion? |
|
This does not need to be merged yet but it might be useful if users want to perform sensitivity analysis |
|
@smartie2076 I placed an example of the code used for my sensitivity analysis in this PR under |
d079264 to
8c50877
Compare
Check for KPI_COST_MATRIX and KPI_SCALAR_MATRIX
…vity_experiment_parameters_groups.csv`
…stivity analysis
…e` - Copy complete module from pv compare (https://github.com/greco-project/pvcompare/blob/f067280558231b2eefafb38fb33023e6cc2144e4/pvcompare/check_inputs.py)" This reverts commit 24d9f7c2
…vcompare - Copy complete module `utils.analysis` of PV compare (https://github.com/greco-project/pvcompare/blob/f067280558231b2eefafb38fb33023e6cc2144e4/pvcompare/analysis.py) to MVS
- changes to `A0` - Add `RUN_SENSITIVITY` to `constants.py`
- Replace `_` with spaces - Use intuitive labels and correct units (from `docs/MVS_kpis_list.csv` and `docs/MVS_parameter_list.csv`
0f5fa90 to
86c85dd
Compare
Fix #813
Changes proposed in this pull request:
mvs_reportwith a single json_with_results file.The following steps were realized, as well (if applies):
black . --exclude docs/)EXECUTE_TESTS_ON=master pytest)Please mark above checkboxes as following:
❌ Check not applicable to this PR
For more information on how to contribute check the CONTRIBUTING.md.