parametric case name

[VictorG]

Dear forum members,

do you have a method to change the parametric default case name ?

I am forced to use the pattern casename~xxxx, I would prefer to have the ability to choose more explicit case names than the suffix ~xxxx.

Thanks
Victor

[AKanudia]

The reports functionality has elaborate means to name and classify scenarios.

[VictorG]

Alright thanks, this is at the result processing step, then I assume it is not possible to change the casename in the run or vd file name with veda features.

Is the reports functionnality still available to ETSAP licences ? It is blocked on my veda4.0.1.0

[AKanudia]

Well, ETSAP members were not really responding to my Reports offer so I withdrew it.

[VictorG]

Well, ETSAP members were not really responding to my Reports offer so I withdrew it.

thanks for the reply

[Antti-L]

> I assume it is not possible to change the casename in the run or vd file name with veda features.

It is possible to do with the GDX2VEDA feature.  You can supply the name of the case in that call:

> gdx2veda gdx vdd [run]

Here, run is the VEDA Run identifier (optional).  That identifier will be the case name when the vd* files for the case are imported. I am regularly using this feature.

[VictorG]

Thanks, I will try to play with attributes like CmdF_bot to modify the case_name

[janis]

Thanks, I will try to play with attributes like CmdF_bot to modify the case_name

I am wondering if you manage to change the parametric case name? How it looks in the VEDA scenario template?

[VictorG]

I actually gave up on this, I work with dictionaries that map case names in my result processing workflow.
Do you have any idea ?

[janis]

Thanks, unfortunately no ideas. I also encountered this issue but realized that I can't solve it in a reasonable amount of time.

[Antti-L]

> I am wondering if you manage to change the parametric case name?

I just tested it, and it works basically well.  You can define whatever names for the parametric scenario cases in the Scen_Par* scenario file, such that the *.VD* files are generated with those names when running GDX2VEDA.

The only problem is that when the names are user-defined like this, VEDA cannot import the VD files automatically. But importing them manually is reasonably easy, because all the latest VD files are shown in the dialog, and so quite easy to select.

[VictorG]

> I am wondering if you manage to change the parametric case name?

I just tested it, and it works basically well.  You can define whatever names for the parametric scenario cases in the Scen_Par* scenario file, such that the *.VD* files are generated with those names when running GDX2VEDA.

The only problem is that when the names are user-defined like this, VEDA cannot import the VD files automatically. But importing them manually is reasonably easy, because all the latest VD files are shown in the dialog, and so quite easy to select.

Could you share an excel file of parametric cases which modified names please ?

[Antti-L]

Attached is a file that worked well in my test on Windows. On Linux it won't work as such.

[VictorG]

Attached is a file that worked well in my test on Windows. On Linux it won't work as such.

Thanks, it works to change the vd file names. My first question was to be able to handle the case name also inside the veda interface like in the browse or case folder names. I think it is not possible to do with the current configuration.

Thanks for the help

[Antti-L]

I can see the cases in the VEDA interface with their new user-defined names (Results Module):

     

You were looking at Browse, which is for model data in those runs. Indeed, the new names are only names assigned for the model results cases, and not for the input datasets. I agree that renaming the input data scenarios is not possible to do inside the interface, only the results cases.