Order of analytics execution

[rkapl123]

Dear all!

In an old ORE version (1.6), the VAR analysis was run AFTER the sensitivity analysis, making it possible to run this in one go:
ORE starting
Reference... OK
Curve configuration... OK
Market data loader... OK
Market... OK
Engine factory... OK
Portfolio... OK
Curve Report... OK
NPV Report... OK
Additional Results... OK
TodaysMarket Calibration... OK
Cashflow Report... OK
Write Base Scenario... SKIP
Sensitivity Report... OK
Stress testing... SKIP
Parametric VaR Report... OK

Now it's the other way round:
Loading inputs OK
Requested analytics CASHFLOW,NPV,PARAMETRIC_VAR,SENSITIVITY
Risk: Build Market for VaR OK
Risk: Build Portfolio for VaR OK
Risk: VaR Calculation OK
Pricing: Build Market OK
Pricing: Build Portfolio OK
Pricing: Cashflow Report OK
Pricing: NPV Report OK
Pricing: Curves Report OK
Risk: Sensitivity Report OK

I see from the definition of std::setstd::string analytics_ in https://github.com/OpenSourceRisk/Engine/blob/master/OREAnalytics/orea/app/inputparameters.hpp#L789 that the analytics are a set and can't be ordered by definition, but this would really reduce a lot of extra calls.

Would it hurt to change that into a std::vector?

I‘ve also seen that the std::set is returning its constituents in ordered Fashion (alphabetically) and the reason why the var analytics is now before the scenario analysis is the renaming to PARAMETRIC_VAR (in 1.8.9 it was VAR).
would it be possible to rename it to VAR_PARAMETRIC (and historical var to VAR_HISTSIM) so it could then be run after SENSITIVITY? This would be the simplest solution.

-regards,
Roland