[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GEMPAK #QRD-654061]: Confirmed: Decoder still broken.
- Subject: [GEMPAK #QRD-654061]: Confirmed: Decoder still broken.
- Date: Wed, 12 Aug 2015 10:05:29 -0600
Hi Ryan,
Thanks for getting back about this. I'm currently working on a Debian 8 build
using a virtual machine, but I'm not quite there. I will let you know when the
build is complete and I can check on the dcwarn decoder.
-Michael
> Michael please see below. I might have sent to wrong address (I just had
> @ucar, no unidata).
>
> Ryan
>
> Begin forwarded message:
>
> > From: Ryan <address@hidden>
> > Date: August 6, 2015 at 6:21:05 PM CDT
> > To: Michael James <address@hidden>
> > Cc: John Hart <address@hidden>
> > Subject: Confirmed: Decoder still broken.
> >
> > Michael,
> >
> > I can again confirm that the warning decoder remains broken, even with
> > those fortran changes.
> >
> > On new Debian 8 machine, In $OBS/storm/warn, all the files are zero length .
> >
> > Now if I go back to my old machine that uses Debian 6, everything is fine.
> >
> > The logfile is ~ldm/data/gempak/logs/dcwarn.log.
> >
> > Please let me know what I need to send you so we can fix this. I cannot
> > keep using operating systems that are years old, we MUST upgrade. Plus,
> > Debian is a very popular OS for servers, other might have this same issue.
> >
> > FYI, I added the fortran flag that you mentioned to the linux64,
> > linux64_g77, and linux64_gfortran versions of Makeinc before I compiled.
> >
> > I will do anything to help fix this my well being depends on it please help.
> >
> > Ryan
> >
> >
> >> On Wed, Aug 5, 2015 at 10:17 PM, Ryan <address@hidden> wrote:
> >
> >> FYI, ssh just like you do for davinci except port 6077 and 6088
> >>
> >> root, tiger (or pub key and bunny con bangs)
> >>
> >> Ryan
> >>
> >>
> >>> On Aug 5, 2015, at 10:05 PM, John Hart <address@hidden> wrote:
> >>>
> >>> The only thing that clearly did not work was the warning decoder. It
> >>> created zero-length files in the $OBS/warn directory. If there were
> >>> other problems, I do not remember them.
> >>>
> >>>
> >>>> On Wed, Aug 5, 2015 at 7:02 PM, Ryan <address@hidden> wrote:
> >>>> I built gempak on NP1 before I left for work.
> >>>>
> >>>> LDM file is in /home/LDM but not installed yet.
> >>>>
> >>>> I hope to have it all done tonight. So next step is to determine if
> >>>> fortran flag worked.
> >>>>
> >>>> Please tell me what it was that was broken before, and how I can test
> >>>> whether or not it's fixed. Tell me. I want to know tomorrow
> >>>>
> >>>> Ryan
> >
> >
> >
> > Ryan
> >
> >
> >> On Aug 5, 2015, at 3:25 PM, Michael James <address@hidden> wrote:
> >>
> >> I believe Makeinc.linux64_gfortran is the file you will use, but that's
> >> just a guess since I've not installed on debian before.
> >>
> >> Michael James
> >> Unidata Program Center
> >> Boulder, CO
> >>
> >>> On Wed, Aug 5, 2015 at 2:15 PM, corepuncher <address@hidden> wrote:
> >>> Michael,
> >>>
> >>> Going to try installing GEMPAK on my Debian 8 system.
> >>>
> >>> However, which Makeinc file do I edit to add this:
> >>>
> >>> FOPT = -fno-whole-file -fno-second-underscore -fno-range-check
> >>> -fd-lines-as-comments $(GEMINC) $(PYINC) -g #-O
> >>>
> >>>
> >>> I do not have Fedora, I have debian. How can I tell which Makeinc it's
> >>> going to use?
> >>>
> >>> Thanks.
> >>
>
>
Ticket Details
===================
Ticket ID: QRD-654061
Department: Support GEMPAK
Priority: Normal
Status: Open