teqc Digest, Vol 183, Issue 3
Mike Rost
rost at unavco.org
Wed Sep 18 20:37:40 UTC 2019
You can look at this past posting from the teqc mailing list and try to
contact the people who developed the teqcplot python script.
-Mike Rost
Software Engineer III
UNAVCO
https://postal.unavco.org/pipermail/teqc/2015/002019.html
On Wed, Sep 18, 2019 at 1:09 PM Ashraf Mousa <ashrafmousa07 at yahoo.com>
wrote:
> I am using teqc to QC a GNSS file with plot option.
> I would like to plot the results.
> I found TEQCPLOT. However, it seems that the teqcplot does not support the
> new format compact 3. It seems to support only the old format "compat"
> Is their any work around to make the teqcplot accept compact3 or to
> downgrade the compact3 to compat.
> Thanks in advance
>
> Prof. Ashraf ElKutb Mousa
>
> Prof. of Geodesy, Senior Geodesist
>
> Crustal Movement lab
>
> Geodynamic Dept.
>
> National Research Institute of Astronomy and Geophysics, Helwan, Cairo
>
> Mob. : +002-01061087313
>
> Tel (home): +002-22-5187001
>
> Tel (Work): +002-22-5541100 (ext. 347)
>
> Fax (Work): +002-22-5548020
>
>
> On Wednesday, September 18, 2019, 07:07:28 PM GMT+3, <
> teqc-request at postal.unavco.org> wrote:
>
>
> Send teqc mailing list submissions to
> teqc at postal.unavco.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://postal.unavco.org/mailman/listinfo/teqc
> or, via email, send a message with subject or body 'help' to
> teqc-request at postal.unavco.org
>
> You can reach the person managing the list at
> teqc-owner at postal.unavco.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of teqc digest..."
>
>
> Today's Topics:
>
> 1. Re: teqc builds very old? (Mike Rost)
> 2. Re: teqc builds very old? (Douglas Hunt)
> 3. Re: teqc builds very old? (Mike Rost)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 18 Sep 2019 08:58:57 -0600
> From: Mike Rost <rost at unavco.org>
> To: Anders Wallin <anders.e.e.wallin at gmail.com>
> Cc: teqc at unavco.org
> Subject: Re: teqc builds very old?
> Message-ID:
> <CANvP6KoKE7UBUzpY37ARczQ3mFbE3ri8JXMbMG4hWFv24N2efw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> No teqc code can not be released under a GPL as it contains source code to
> access manufacturer data formats that are under a non-disclosure agreement.
>
> -M
>
> Mike Rost
> Software Engineer III
> UNAVCO
>
>
> On Tue, Sep 17, 2019 at 10:38 PM Anders Wallin <
> anders.e.e.wallin at gmail.com>
> wrote:
>
> > Does UNAVCO have a roadmap for making the teqc source available under an
> > open license? (maybe it already is? - but I found only binaries on the
> > website...)
> > If the source is hosted on e.g. github under a suitable license there
> > could be a community of users from various institutions that can provide
> at
> > least minimal maintenance (e.g. as OSs and libraries evolve)
> >
> > Anders
> >
> > On Tue, Sep 17, 2019 at 5:54 PM Frederick Blume <blume at unavco.org>
> wrote:
> >
> >> All,
> >>
> >> Firstly, there will be no further updates too teqc. It is frozen in
> time
> >> as currently posted, with the final version dated 2019Feb25.
> >>
> >> However the fact that the executables are tagged with older versions of
> a
> >> given OS does not indicate lack of compatibility with current
> versions. In
> >> the case of the Mac OS X version, I am happily running the final teqc
> >> compilation on OS X 10.14.6 in spite of the fact that it was compiled
> on a
> >> Mac running an earlier version of the OS. We had been doing this to
> ensure
> >> backwards compatibility with older OS versions.
> >>
> >> In the case of Yolande?s linux version, the fact that teqc was compiled
> >> on linux 2.x does not mean it won?t run on 5.x - download it and give
> it a
> >> try. As the note *1 on the downloads page indicates:
> >>
> >> "*1 crashes of one or the other build have occurred on various Linux
> >> releases; if you have tried the statically-linked build and it crashes,
> try
> >> the dynamically-linked build, or vice versa "
> >>
> >>
> >>
> >> Best,
> >> Freddy B.
> >>
> >> ====================
> >> Dr. Frederick Blume
> >> Sr. Project Manager
> >> UNAVCO
> >> 6350 Nautilus Dr.
> >> Boulder, CO 80301-5553
> >> (303)579-9952
> >> http://www.unavco.org
> >> ====================
> >>
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://postal.unavco.org/pipermail/teqc/attachments/20190918/869c9ee3/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Wed, 18 Sep 2019 09:46:40 -0600
> From: Douglas Hunt <dhunt at ucar.edu>
> To: Mike Rost <rost at unavco.org>
> Cc: teqc at unavco.org, cosmicops <cosmicops at ucar.edu>
> Subject: Re: teqc builds very old?
> Message-ID: <1e698388-bda4-5cd5-e3e6-0745ded6c88b at ucar.edu>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Mike:? Is there any way to disentagle the non-disclosure code from
> the rest of teqc?? It would be a pity to lose teqc as a viable tool just
> because Lou retired.? Our project at UCAR/CDAAC uses teqc all over, and
> we have been willing to accept binary-only code since we assumed it
> would be supported by UNAVCO.
>
> Regards,
>
> ? Doug Hunt
> ? UCAR/COSMIC
> ? Software Engineer IV
>
> On 9/18/19 8:58 AM, Mike Rost wrote:
> > No teqc code can not be released under a GPL as it contains source
> > code to access manufacturer data formats that are under a
> > non-disclosure agreement.
> >
> > -M
> >
> > Mike Rost
> > Software Engineer III
> > UNAVCO
> >
> >
> > On Tue, Sep 17, 2019 at 10:38 PM Anders Wallin
> > <anders.e.e.wallin at gmail.com <mailto:anders.e.e.wallin at gmail.com>>
> wrote:
> >
> > Does UNAVCO have a roadmap for making the teqc source available
> > under an open license? (maybe it already is? - but I found only
> > binaries on the website...)
> > If the source is hosted on e.g. github under a suitable license
> > there could be a community of users from various institutions that
> > can provide at least minimal maintenance (e.g. as OSs and
> > libraries evolve)
> >
> > Anders
> >
> > On Tue, Sep 17, 2019 at 5:54 PM Frederick Blume <blume at unavco.org
> > <mailto:blume at unavco.org>> wrote:
> >
> > All,
> >
> > Firstly, there will be no further updates too teqc.? It is
> > frozen in time as currently posted, with the final version
> > dated?2019Feb25.
> >
> > However the fact that the executables are tagged with older
> > versions of a given OS does not indicate lack of compatibility
> > with current versions.? In the case of the Mac OS X version, I
> > am happily running the final teqc compilation on OS X 10.14.6
> > in spite of the fact that it was compiled on a Mac running an
> > earlier version of the OS.? We had been doing this to ensure
> > backwards compatibility with older OS versions.
> >
> > In the case of Yolande?s linux version, the fact that teqc was
> > compiled on linux 2.x does not mean it won?t run on 5.x -
> > download it and give it a try.? As the note *1 on the
> > downloads page indicates:
> >
> > "*1?crashes of one or the other build have occurred on various
> > Linux releases; if you have tried the statically-linked build
> > and it crashes, try the dynamically-linked build, or vice versa "
> >
> >
> >
> > Best,
> > Freddy B.?
> >
> > ====================
> > Dr. Frederick Blume
> > Sr. Project Manager
> > UNAVCO
> > 6350 Nautilus Dr.
> > Boulder, CO ?80301-5553
> > (303)579-9952
> > http://www.unavco.org
> > ====================
> >
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://postal.unavco.org/pipermail/teqc/attachments/20190918/d5026981/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Wed, 18 Sep 2019 10:06:47 -0600
> From: Mike Rost <rost at unavco.org>
> To: Douglas Hunt <dhunt at ucar.edu>
> Cc: teqc at unavco.org, cosmicops <cosmicops at ucar.edu>
> Subject: Re: teqc builds very old?
> Message-ID:
> <CANvP6KpWVFREdTbgJm=6yVN47ObRTonGykFO31+wrV_LFzMi6g at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Doug, there isn't a simple answer to your question.
>
> Yes it is possible to drop native receiver support, but it's not
> economically feasible to separate out that code and teqc's deep dependance
> on those headers. With the decision to freeze teqc, there is no ongoing
> work on the code base, and no future requirements for development.
>
> You are not alone in your concerns of transitioning from teqc as our
> process is deeply entrenched in the teqc code and the change is not going
> to be easy or painless.
>
> -Mike
>
> On Wed, Sep 18, 2019 at 9:46 AM Douglas Hunt <dhunt at ucar.edu> wrote:
>
> > Hi Mike: Is there any way to disentagle the non-disclosure code from the
> > rest of teqc? It would be a pity to lose teqc as a viable tool just
> > because Lou retired. Our project at UCAR/CDAAC uses teqc all over, and
> we
> > have been willing to accept binary-only code since we assumed it would be
> > supported by UNAVCO.
> >
> > Regards,
> >
> > Doug Hunt
> > UCAR/COSMIC
> > Software Engineer IV
> >
> > On 9/18/19 8:58 AM, Mike Rost wrote:
> >
> > No teqc code can not be released under a GPL as it contains source code
> to
> > access manufacturer data formats that are under a non-disclosure
> agreement.
> >
> > -M
> >
> > Mike Rost
> > Software Engineer III
> > UNAVCO
> >
> >
> > On Tue, Sep 17, 2019 at 10:38 PM Anders Wallin <
> > anders.e.e.wallin at gmail.com> wrote:
> >
> >> Does UNAVCO have a roadmap for making the teqc source available under an
> >> open license? (maybe it already is? - but I found only binaries on the
> >> website...)
> >> If the source is hosted on e.g. github under a suitable license there
> >> could be a community of users from various institutions that can
> provide at
> >> least minimal maintenance (e.g. as OSs and libraries evolve)
> >>
> >> Anders
> >>
> >> On Tue, Sep 17, 2019 at 5:54 PM Frederick Blume <blume at unavco.org>
> wrote:
> >>
> >>> All,
> >>>
> >>> Firstly, there will be no further updates too teqc. It is frozen in
> >>> time as currently posted, with the final version dated 2019Feb25.
> >>>
> >>> However the fact that the executables are tagged with older versions of
> >>> a given OS does not indicate lack of compatibility with current
> versions.
> >>> In the case of the Mac OS X version, I am happily running the final
> teqc
> >>> compilation on OS X 10.14.6 in spite of the fact that it was compiled
> on a
> >>> Mac running an earlier version of the OS. We had been doing this to
> ensure
> >>> backwards compatibility with older OS versions.
> >>>
> >>> In the case of Yolande?s linux version, the fact that teqc was compiled
> >>> on linux 2.x does not mean it won?t run on 5.x - download it and give
> it a
> >>> try. As the note *1 on the downloads page indicates:
> >>>
> >>> "*1 crashes of one or the other build have occurred on various Linux
> >>> releases; if you have tried the statically-linked build and it
> crashes, try
> >>> the dynamically-linked build, or vice versa "
> >>>
> >>>
> >>>
> >>> Best,
> >>> Freddy B.
> >>>
> >>> ====================
> >>> Dr. Frederick Blume
> >>> Sr. Project Manager
> >>> UNAVCO
> >>> 6350 Nautilus Dr.
> >>> Boulder, CO 80301-5553
> >>> (303)579-9952
> >>> http://www.unavco.org
> >>> ====================
> >>>
> >>
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://postal.unavco.org/pipermail/teqc/attachments/20190918/c25c6be5/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> teqc mailing list
> teqc at postal.unavco.org
> https://postal.unavco.org/mailman/listinfo/teqc
>
> ------------------------------
>
> End of teqc Digest, Vol 183, Issue 3
> ************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://postal.unavco.org/pipermail/teqc/attachments/20190918/f3473e69/attachment-0001.html>
More information about the teqc
mailing list