[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20051011: status of 4 CIMSS products formerly in IDD UNIWISC feed



>From:  Jim Nelson <address@hidden>
>Organization:  SSEC
>Keywords:  200510112005.j9BK5reX022636 CIMSS sounder products

Hi Jim,

>Greetings, Tom -- I'm sorry I didn't get back to you yesterday (10/10) 
>-- a tough day.   :(

No worries.  I've been busy too ;-)

>But today is a  *new*  day!    BTW, are you going to make it to the MUG 
>meeting?!

Yup, I'll be there.

>At any rate, I'm investigating the CIMSSP/FIRESNH, FIRESSH, GCOZONE,
>and GERSST ADDE datasets that UNIDATA is attempting to access, per the
>emails below.  I must admit that I had lost track of these datastreams
>over time -- there are so many of them these days!

I agree.

>Furthermore, we
>are in the process right now of migrating off of our last AIX box
>(we're going totally Linux), so we'll be trying to prune those
>datastreams that appear to no longer be needed by anybody.

OK.

>1.) Concerning the  FIRE*  datasets -- I talked with Chris Schmit here 
>    at CIMSS. They inadvertently broke when the ABBA processing here at CIMSS 
>    was migrated from one system to another some time ago.  We can 
> re-establish 
>    those two datasets, but we're concerned that apparently nobody noticed for
>    8 months that they were missing.

It was my fault for not getting back to you folks when I first noticed way
back in February that they were missing.  No excuses for that lapse...

>      We just want to avoid producing data for the sake of producing 
>      it.   Any opinions?

I understand.  The wildfire ABBA products are (at least were) used by
our users in the southern hemisphere (mostly Brazil), and the chair of
our Users Committee had at one time requested that additional products
like this be created from GOES-West.  So, I can say that folks will
look at the products if they are available.

>2.) GCOZONE --  I have talked with Chris Schmidt about this one, too.   
>    We are producing a regression-based, Single FOV (SFOV) combined (all 4 
>    sectors) ozone DPI areafile (all 24 hours). It is being served via the
>    following ADDE dataset: EDWARD/GCOZONE,
>    where EDWARD =   DATALOC  ADD  EDWARD  EDWARD.SSEC.WISC.EDU
>
>    Use  PRDUTIL  to see the calibration being used.  It is 100->500 Dobson
>    units mapped into brightness levels 2->201.
>
>    see also:   http://cimss.ssec.wisc.edu/goes/realtime  and look for ozone.

Nice!

>    Of course,  if you wish to create the gifs you see at the above Web
>    address, you will need several virtual graphics, an enhancement curve,
>    etc.  Let me know if you have any interest in getting these.

Since columnar ozone displays are not available to the Unidata
community in NOAAPORT, I am interested in making this product available
in our UNIWISC IDD datastream.  Is it OK to access the EDWARD products
on an ongoing basis?  If yes, I will create a stretch table using the
value mapping you include above (so BAR can correctly label the
displays).

>3.) GERSST   --  This one is pretty old, and regardless of what it 
>    contained in the past, I would suggest using instead the same SST
>    areafile that CIMSS pulls over from NESDIS, from the dataset and
>    position PLB/RSST.1. It would be best if you requested permission
>    to the PLB group from NESDIS directly, by sending an email 
>    to Russ Lancaster (address@hidden).
>
>    By the way,  PLB  gets mapped into  140.90.195.89 
> (gp19.ssd.nesdis.noaa.gov)
>    in your MCTABLE.TXT.

OK, thanks.  I went through the process of getting access to the SATEPS
ADDE servers quite some time ago.  I am able to access the PLB/RSST here
at Unidata, and I should be able to access at the IDD injection machine at
SSEC, unidata2.ssec.wisc.edu.

>Thank you, Tom.   I will await your response!

So, the issue boils down to whether or not you folks want/are willing
to restart the generation of the wildfire ABBA products.  If you are
willing to do this, I will make sure that they are included in the
UNIWISC IDD datastream for the Unidata community.

By the way, the other products that would be MOST useful/interesting are
IR and WV composites over the North Pole (as a complement to the one
being created by the AMRC folks).  I will be talking to Matthew L.
about this some more, but I figured that it couldn't hurt mentioning
it to you/Chris if they generated somewhere in CIMSS

Thanks for your help!

Cheers,

Tom

>---
>-------- Original Message --------
>Subject:       [Fwd: 20051007: status of 4 CIMSS products formerly in IDD 
>UNIWISC feed]
>Date:  Mon, 10 Oct 2005 09:31:37 -0500
>From:  Jerrold Robaidek <address@hidden>
>To:    Jim Nelson <address@hidden>, Gary Wade 
><address@hidden>
>
>
>
>Hi Guys,
>
>I think you helped Tom set these up quite a while back, do you know where 
>these datasets
>  
>now reside?
>
>Thanks,
>
>
>Jerry
>
>-------- Original Message --------
>Subject: 20051007: status of 4 CIMSS products formerly in IDD UNIWISC feed
>Date: Fri, 07 Oct 2005 14:11:20 -0600
>From: Unidata Support <address@hidden>
>Reply-To: address@hidden
>Organization: UCAR/Unidata
>To: Jerrold Robaidek <address@hidden>, address@hidden
>CC: address@hidden
>
>>From: Unidata User Support <address@hidden>
>>Organization: Unidata Program Center/UCAR
>>Keywords: IDD UNIWISC CIMSS products
>
>Hi,
>
>I have (finally) been reviewing the content of the UNIWISC IDD
>datastream that is created on unidata2.ssec.wisc.edu, and I have found
>that four images that used to be transferred from the ADDE CIMSSP
>dataset on vern.ssec.wisc.edu are no long are available:
>
>CIMSSP/FIRESNH
>CIMSSP/FIRESSH
>CIMSSP/GCOZONE
>CIMSSP/GERSST
>
>The CIMSSP/FIRESNH, CIMSSP/FIRESSH, and CIMSSP/GERSST datasets are
>still defined, but are not being updated (last update for the FIRES*H
>products was back in February; there are no elements in the GERSST
>dataset).  CIMSSP/GCOZONE is no longer defined.
>
>Questions:
>
>- are the FIRES*H products still being created?  If yes, are current
>  images available on a different ADDE server?
>
>- is a SST product still being created?  If yes, where can I access it?
>
>- is there an Ozone product being generated anywhere?  If yes, where
>  can I access it?
>
>Thanks in advance for any help you can provide!
>
>Cheers
>
>Tom
>
>
>-- 
>Jerrold Robaidek                       Email:  address@hidden
>SSEC Data Center                       Phone: (608) 262-6025
>University of Wisconsin                Fax: (608) 263-6738
>Madison, Wisconsin
>
>
>--------------080006010001010709080901
>Content-Type: text/html; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
><!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
><html>
><head>
>  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
>  <title></title>
></head>
><body text="#000000" bgcolor="#ffffff">
><meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
><title></title>
>Greetings, Tom -- I'm sorry I didn't get back to you yesterday (10/10)
>-- a tough day.&nbsp;&nbsp; :(<br>
>But today is a&nbsp; *new*&nbsp; day!&nbsp;&nbsp;&nbsp; BTW, are you going to 
>make it to
>  the MUG
>meeting?!<br>
><br>
>At any rate, I'm investigating the CIMSSP/FIRESNH, FIRESSH, GCOZONE,
>and&nbsp; GERSST<br>
>ADDE datasets that UNIDATA is attempting to access, per the emails
>below.&nbsp;&nbsp; I must admit that<br>
>I had lost track of these datastreams over time -- there are so many of
>them these days!&nbsp;&nbsp; Furthermore,<br>
>we are in the process right now of migrating off of our last AIX box
>(we're going totally Linux), so we'll<br>
>be trying to prune those datastreams that appear to no longer be needed
>by anybody.<br>
><br>
>1.)&nbsp; Concerning the&nbsp; FIRE*&nbsp; datasets -- I talked with Chris 
>Schmit here
>at CIMSS.&nbsp; <br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; They inadvertently broke when the ABBA 
>processing here at
>  CIMSS
>was migrated <br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from one system to another some time ago.&nbsp; 
>We can re
> -establish
>those two datasets,<br>
>&nbsp; &nbsp; &nbsp; but we're concerned that apparently nobody noticed for 8 
>months
>that they were missing. <br>
>&nbsp; &nbsp; &nbsp; We just want to avoid producing data for the sake of 
>producing
>it.&nbsp;&nbsp; Any opinions?<br>
><br>
>2.)&nbsp; GCOZONE --&nbsp; I have talked with Chris Schmidt about this one,
>too.&nbsp;&nbsp; We are producing a regression-based,<br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
> nbsp; Single FOV (SFOV) combined (all 4
>sectors) ozone DPI areafile (all 24 hours).&nbsp; <br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
> nbsp; It is being served via the following
>ADDE dataset:&nbsp;&nbsp;&nbsp; EDWARD/GCOZONE,<br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
> nbsp; where EDWARD =&nbsp;&nbsp; DATALOC&nbsp; ADD&nbsp; EDWARD&nbsp;
>EDWARD.SSEC.WISC.EDU<br>
><br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
> nbsp; Use&nbsp; PRDUTIL&nbsp; to see the calibration
>being used.&nbsp; It is 100-&gt;500 Dobson units mapped<br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
> nbsp; into brightness levels 2-&gt;201.<br>
><br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
> nbsp; see also:&nbsp;&nbsp;
><a class="moz-txt-link-freetext" 
>href="http://cimss.ssec.wisc.edu/goes/realtime";>http://
> cimss.ssec.wisc.edu/goes/realtime</a>&nbsp;&nbsp;&nbsp; and look for 
> ozone.<br>
><br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
> nbsp; Of course,&nbsp; if you wish to create the
>gifs you see at the above Web address, you <br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
> nbsp; will need several virtual graphics, an
>enhancement curve, etc.&nbsp; Let me know if you<br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
> nbsp; have any interest in getting these.<br>
><br>
>3.)&nbsp; GERSST&nbsp;&nbsp; --&nbsp; This one is pretty old, and regardless 
>of what it
>contained in the past, I would suggest using<br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>  instea
> d the same SST&nbsp; areafile that CIMSS
>pulls over from NESDIS, from the dataset and <br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>  positi
> on&nbsp;&nbsp; PLB/RSST.1.&nbsp;&nbsp; It would be best
>if you requested permission to the PLB group<br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>  from N
> ESDIS directly, by sending an email
>to Russ Lancaster (<a class="moz-txt-link-abbreviated" 
>href="mailto:russell.lancaster@no
> aa.gov">address@hidden</a>).<br>
><br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>  By the
>  way,&nbsp; PLB&nbsp; gets mapped into&nbsp;
>140.90.195.89 (gp19.ssd.nesdis.noaa.gov) in your<br>
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
> p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>  MCTABL
> E.TXT.<br>
><br>
>Thank you, Tom.&nbsp;&nbsp; I will await your response!<br>
><br>
>Sincerely, <br>
><br>
>Jim<br>
>---<br>
>-------- Original Message --------
><table cellpadding="0" cellspacing="0" border="0">
>  <tbody>
>    <tr>
>      <th valign="baseline" align="right" nowrap="nowrap">Subject: </th>
>      <td>[Fwd: 20051007: status of 4 CIMSS products formerly in IDD
>UNIWISC feed]</td>
>    </tr>
>    <tr>
>      <th valign="baseline" align="right" nowrap="nowrap">Date: </th>
>      <td>Mon, 10 Oct 2005 09:31:37 -0500</td>
>    </tr>
>    <tr>
>      <th valign="baseline" align="right" nowrap="nowrap">From: </th>
>      <td>Jerrold Robaidek <a class="moz-txt-link-rfc2396E"
> href="mailto:address@hidden";>&lt;address@hidden&gt;</a></td>
>    </tr>
>    <tr>
>      <th valign="baseline" align="right" nowrap="nowrap">To: </th>
>      <td>Jim Nelson <a class="moz-txt-link-rfc2396E"
> href="mailto:address@hidden";>&lt;address@hidden&gt;</a>,
>Gary Wade
>      <a class="moz-txt-link-rfc2396E"
> href="mailto:address@hidden";>&lt;address@hidden&gt;</a></td>
>    </tr>
>  </tbody>
></table>
><br>
><br>
><pre>Hi Guys,
>
>I think you helped Tom set these up quite a while back, do you know where 
>these datasets
>  
>now reside?
>
>Thanks,
>
>
>Jerry
>
>-------- Original Message --------
>Subject: 20051007: status of 4 CIMSS products formerly in IDD UNIWISC feed
>Date: Fri, 07 Oct 2005 14:11:20 -0600
>From: Unidata Support <a
> class="moz-txt-link-rfc2396E" href="mailto:address@hidden";>&lt;support@unidat
> a.ucar.edu&gt;</a>
>Reply-To: <a
> class="moz-txt-link-abbreviated" href="mailto:address@hidden";>support@unidata
> .ucar.edu</a>
>Organization: UCAR/Unidata
>To: Jerrold Robaidek <a
> class="moz-txt-link-rfc2396E" 
> href="mailto:address@hidden";>&lt;address@hidden&g
> t;</a>, <a
> class="moz-txt-link-abbreviated" href="mailto:address@hidden";>datacenter@ssec
> .wisc.edu</a>
>CC: <a
> class="moz-txt-link-abbreviated"
> href="mailto:address@hidden";>address@hidden</
> a>
>
>&gt;From: Unidata User Support <a
> class="moz-txt-link-rfc2396E" href="mailto:address@hidden";>&lt;support@unidat
> a.ucar.edu&gt;</a>
>&gt;Organization: Unidata Program Center/UCAR
>&gt;Keywords: IDD UNIWISC CIMSS products
>
>Hi,
>
>I have (finally) been reviewing the content of the UNIWISC IDD
>datastream that is created on unidata2.ssec.wisc.edu, and I have found
>that four images that used to be transferred from the ADDE CIMSSP
>dataset on vern.ssec.wisc.edu are no long are available:
>
>CIMSSP/FIRESNH
>CIMSSP/FIRESSH
>CIMSSP/GCOZONE
>CIMSSP/GERSST
>
>The CIMSSP/FIRESNH, CIMSSP/FIRESSH, and CIMSSP/GERSST datasets are
>still defined, but are not being updated (last update for the FIRES*H
>products was back in February; there are no elements in the GERSST
>dataset).  CIMSSP/GCOZONE is no longer defined.
>
>Questions:
>
>- are the FIRES*H products still being created?  If yes, are current
>  images available on a different ADDE server?
>
>- is a SST product still being created?  If yes, where can I access it?
>
>- is there an Ozone product being generated anywhere?  If yes, where
>  can I access it?
>
>Thanks in advance for any help you can provide!
>
>Cheers
>
>Tom
>**************************************************************************** 
>&lt;
>Unidata User Support                                    UCAR Unidata Program 
>&lt;
>(303)497-8643                                                  P.O. Box 3000 
>&lt;
><a class="moz-txt-link-abbreviated"
> href="mailto:address@hidden";>address@hidden</a>                    
>                Boulder, CO 80307 &lt;
>---------------------------------------------------------------------------- 
>&lt;
>Unidata WWW Service              <a
> class="moz-txt-link-freetext"
> href="http://my.unidata.ucar.edu/content/support";>http://my.unidata.ucar.edu/content/su
> pport</a>  &lt;
>**************************************************************************** 
>&lt;
>
>
>-- 
>Jerrold Robaidek                       Email:  <a
> class="moz-txt-link-abbreviated" 
> href="mailto:address@hidden";>address@hidden</a
> >
>SSEC Data Center                       Phone: (608) 262-6025
>University of Wisconsin                Fax: (608) 263-6738
>Madison, Wisconsin
></pre>
></body>
></html>
>
>--------------080006010001010709080901--
>
Cheers,

Tom
--
+-----------------------------------------------------------------------------+
* Tom Yoksas                                             UCAR Unidata Program *
* (303) 497-8642 (last resort)                                  P.O. Box 3000 *
* address@hidden                                   Boulder, CO 80307 *
* Unidata WWW Service                             http://www.unidata.ucar.edu/*
+-----------------------------------------------------------------------------+