drudg additional ds in thread01 procedure

[BeppeMc]

In FS-10.2-alpha1 I found drudg adding a "ds" label in thread01 while this is already done by jive5ab.
results:
drw-r--r-- oper rtx 52.06G Mar 08 10:05 ev024g_mc_no0009_dsds1
drw-r--r-- oper rtx 52.06G Mar 08 10:05 ev024g_mc_no0009_dsds2
drw-r--r-- oper rtx 52.06G Mar 08 10:20 ev024g_mc_no0010_dsds1
drw-r--r-- oper rtx 52.06G Mar 08 10:20 ev024g_mc_no0010_dsds2
drw-r--r-- oper rtx 16.22G Mar 08 10:25 ev024g_mc_no0011_dsds1
drw-r--r-- oper rtx 16.22G Mar 08 10:25 ev024g_mc_no0011_dsds2
Easily solvable editing the procedure.

[haavee]

Hi Beppe, this is a feature. It was discussed at the recent TOG (presentation B Eldering). The official file naming convention (https://vlbi.org/wp-content/uploads/2019/03/049.1b-Filenaming-conventions.pdf) sais that any auxiliary information can be encoded in the file name through the use of a key value pair, formatted in the file name as _<key><value>, where the key is a registered two-character key.
For encoding VEX2 data stream labels we've suggested to register the key ds, and the value would be the data stream label as stored in the VEX2 file. In VEX2 the data stream labels are free form, but the examples have DS0, DS1, ... and it was thought best to stick with that, at least to provide some predictability in the name.
Putting this all together, a key of ds and a data stream label from the VEX2 file DS0, you'll end up with _dsds0 encoded in the file name for the recording of data stream with label DS0.
The lower case for the value is applied by jive5ab; making all tools that need to find a specific recording simpler & more reliable it was decided to force a particular, if arbitrary, case, in this case lower case.

[wehimwich]

We can add a note to explain this in Thread Procedure, but it will still be a bit surprising for those who haven't read it.

[haavee]

Yes, it would be good to document this. Is that the best place to do this <yes it seems to be!>

[BeppeMc]

Ok, thank all for the explanations.