[Difx-users] vex2 has landed {External}

[harro verkouter]

Hi Chris,

Could you submit an issue/PR over here?
https://github.com/nvi-inc/vex

That would give the other interested correlator parties a chance of
reviewing and verifying your patch on other systems.

Cheers,
M

On Mon, 31 Jan 2022 at 07:58, Chris Phillips via Difx-users <
difx-users at listmgr.nrao.edu> wrote:

> Hi Walter,
>
> I have just submitted a patch to "vex.h" which your update clobbered. To
> gex the lexparser to compile on OSX, it needs the compiler definitions I
> have just added. These may well be compiler version differences rather than
> OSX specific. - in which case it will affect everyone once Linux
> distributions move to newer gcc versions (OSX homebrew uses a very recent
> version of the gcc suite).
>
> Maybe we should request these get pushed "back" onto the official FS code
> base.
>
> Cheers
> Chris
>
> On Fri, Jan 28, 2022 at 10:13 AM Walter Brisken via Difx-users <
> difx-users at listmgr.nrao.edu> wrote:
>
>>
>> Hi DiFX Users,
>>
>> I have merged the Goddard/NVI vex2 parser and related vex2difx changes
>> (which were developed under the vex2 branch over the last several months)
>> into the vex2difx trunk.
>>
>> Behavior for vex1.5 files should remain largely unchanged.  There has
>> been
>> a report of an incomplete vex1.5 file that used to work not working
>> anymore -- such non-compliant cases are not likely to receive any
>> development attention :)
>>
>> However, if you see any regression when using a valid vex1.5 file, please
>> send me all the files needed to run vex2difx and I will work to resolve
>> the issue.
>>
>> Support for new vex2 features in vex2difx is not complete and has not
>> been
>> extensively tested -- both due to lack of an adequate supply of vex2
>> files
>> that span the huge space of possible use cases.  Test reports (fails and
>> successes) and sample files would be appreciated.  That said, some of the
>> critical new features (support for the BITSTREAM and DATASTREAM tables
>> that better support Mark5B and VDIF formats) are supported, at least to
>> some degree.
>>
>> The ChangeLog file in the SVN repository has some details on the
>> supported
>> features.
>>
>> The vex2 defining document is available at the NRAO wiki, but note that
>> this location is subject to change:
>>
>> https://safe.nrao.edu/wiki/bin/view/VLBA/Vex2doc
>>
>>
>>         -Walter
>>
>> -------------------------
>> Walter Brisken
>> NRAO
>> Deputy Assistant Director for VLBA Development
>> (505)-234-5912 (cell)
>> (575)-835-7133 (office; not useful during COVID times)
>>
>> _______________________________________________
>> Difx-users mailing list
>> Difx-users at listmgr.nrao.edu
>> https://listmgr.nrao.edu/mailman/listinfo/difx-users
>>
> _______________________________________________
> Difx-users mailing list
> Difx-users at listmgr.nrao.edu
> https://listmgr.nrao.edu/mailman/listinfo/difx-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listmgr.nrao.edu/pipermail/difx-users/attachments/20220131/c698fb1d/attachment.html>