>
>
> > I'd be perfectly happy with a replacement mechanism. I.e. upon adding a
> PV
> > to the group, replace non-supported characters with '_'.
>
> QSRV does not compute group or member names automatically. So I think
> this is a request for whatever person or tool is creating the group
> definition JSON for you.
>
in this case there is no suffix, but you get the idea.
> > There are potentially hundreds of PVs to add to pva-groups.
>
> Hundreds? Please let us know how this works out.
What exactly do you want to know? I assume that pva/QRSV is tested and
benchmarked? I even more desperately hope that this was done with more than
just 'hundreds' of fields in groups!
>
>
> > I'd be perfectly happy with a replacement mechanism. I.e. upon adding a
> PV
> > to the group, replace non-supported characters with '_'.
>
> QSRV does not compute group or member names automatically. So I think
> this is a request for whatever person or tool is creating the group
> definition JSON for you.
>
no tool, simple substitution + template /github. com/paulscherre rinstitute/ ecmccfg/ blob/pva/ db/Beckhoff_ 1XXX/ecmcEL1008 .substitutions /github. com/paulscherre rinstitute/ ecmccfg/ blob/pva/ db/generic/ ecmc_binaryInpu t-chX.template
https:/
https:/
in this case there is no suffix, but you get the idea.
> > There are potentially hundreds of PVs to add to pva-groups.
>
> Hundreds? Please let us know how this works out.
What exactly do you want to know? I assume that pva/QRSV is tested and
benchmarked? I even more desperately hope that this was done with more than
just 'hundreds' of fields in groups!