[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20021101: NFS mount point to LDM data
This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
- Subject: 20021101: NFS mount point to LDM data
- Date: Fri, 01 Nov 2002 10:56:39 -0700
See answer yesterday below. You link to the mcidas AREA files should be such that you can see you images from your links at: ls $SAT/GOES-8/4km/IR/IR_20021101_1215 for example. Assuming your IR_20021101_1215 is a link to your /var/data/mcidas/AREA.... file. Steve Chiswell >From: gempak <address@hidden> >Organization: UCAR/Unidata >Keywords: 200210301827.g9UIRxX14776 >Steve, > We NFS mounted the data after the /var/data/ldm/ point, and everything seems > >to work in Gempak, except we can't get satellite images. The directory >structure takes us to the images which are pointers (links) back to > > /var/data/mcidas/AREA... > > Since /var/data/ldm is also a pointer from /usr/user/ldm/data as well as fr > om > /usr/var/data > > Can we NFS mount at /usr/user? I'm worried about gettign into some sort of > >endless loop of poitners - links. > > If I mount before /var then the links will still work. > > Does this make sense, or am I missing something fundamental here? > > Thank you for your patience. > Nancy > > address@hidden > address@hidden > Nancy, The NFS mount point can be anywhere. If both the server and the client machines have the /usr/user path, then that would be ideal. The $GEMDATA would likely be /usr/user/ldm/data/gempak. If your area files are under /var/data/mcidas, I'm also assuming that this is /usr/user/mcidas, and if so, would be convenient using the NFS mount point above. In GEMPAK, the satellite images are rooted at the $SAT location. You have 2 options. 1) here, I have the ldm-mcidas decoder pnga2area create the files using the tree structure expected by GEMPAK as shown: http://www.unidata.ucar.edu/packages/gempak/tutorial/pqact/images.tbl 2) If your files are named AREA0120, AREA0121, etc, then you can generate symbolic links from those files to a GEMPAK tree structure where the file name provides the data/time band information as above using the areaInfo program. This would be used in the GUI programs for correctly ordering the loops (since the AREA file names are circular and do not give the order). Steve Chiswell >From: Nancy Selover <address@hidden> >Organization: UCAR/Unidata >Keywords: 200211011744.gA1HisX22577 >This message is in MIME format. Since your mail reader does not understand >this format, some or all of this message may not be legible. > >--Boundary_(ID_eWmIL93DXqHsm9zbXDoxoA) >Content-type: text/plain; charset="iso-8859-1" > >Steve, > We are trying to figure out where to NFS mount on the LDM machine so >the other machines running Gempak can access all the data. We originally >put the mount after /var/data/ldm so we could then get to the gempak and >radar subdirectories. That works great for everything except the satellite >imagery. The satellite imagery are not files, but are links to files >contained in the >/var/data/mcidas/area.... subdirectories. > Our file structure is: /usr > /user >/data /var /......... > /ldm /gempak /mcidas /ldm >/data > >/ldm /mcidas > >/gempak /radar > >Once you are at /usr/user/ldm if you cd to either /data or /ldm you >are linked to /var/data/ldm >From there you go to gempak or radar to get to the data. But the satellite >image files are actually links back to /var/data/mcidas/area... > >Can we NFS mount at /usr/user - (i.e. just before /var)?? My concern is >that we don't end up in an endless loop of links. > >Thank you. >Nancy > >Nancy J. Selover >Asst. State Climatologist >Office of Climatology tel: 480-965-0580 >Arizona State University fax: 480-965-1473 >Tempe, AZ 85287-1508 e-mail: address@hidden > > >--Boundary_(ID_eWmIL93DXqHsm9zbXDoxoA) >Content-type: text/html; charset="iso-8859-1" >Content-transfer-encoding: quoted-printable > ><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> ><HTML> ><HEAD> ><META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = >charset=3Diso-8859-1"> ><META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = >5.5.2655.35"> ><TITLE>NFS mount point to LDM data</TITLE> ></HEAD> ><BODY> > ><P><FONT SIZE=3D2 FACE=3D"Arial">Steve,</FONT> ><BR> <FONT SIZE=3D2 = >FACE=3D"Arial">We are trying to figure out where to NFS mount on the = >LDM machine so the other machines running Gempak can access all the = >data. We originally put the mount after /var/data/ldm so we = >could then get to the gempak and radar subdirectories. That works = >great for everything except the satellite imagery. The satellite = >imagery are not files, but are links to files contained in the = ></FONT></P> > ><P><FONT SIZE=3D2 = >FACE=3D"Arial">/var/data/mcidas/area.... &n= >bsp; subdirectories.</FONT> ><BR> <FONT SIZE=3D2 = >FACE=3D"Arial">Our file structure is: /usr</FONT> ><BR> = > = > = > <FONT SIZE=3D2 = >FACE=3D"Arial">/user = > = > = > = > /data = > /var = >/.........</FONT> ><BR> = > = > <FONT SIZE=3D2 = >FACE=3D"Arial">/ldm /gempak /mcidas = > = > /ldm = > /data </FONT> ><BR> = > = > = > = > = > = > = > = > = > = > <FONT SIZE=3D2 = >FACE=3D"Arial">/ldm /mcidas</FONT> ><BR> = > = > = > = > = > = > = > = > = > = > <FONT SIZE=3D2 = >FACE=3D"Arial">/gempak /radar</FONT> ></P> > ><P><FONT SIZE=3D2 FACE=3D"Arial">Once you are at = >/usr/user/ldm if you cd to either /data or = >/ldm you are linked to /var/data/ldm</FONT> ><BR><FONT SIZE=3D2 FACE=3D"Arial">From there you go to gempak or radar = >to get to the data. But the satellite image files are actually = >links back to /var/data/mcidas/area...</FONT></P> > ><P><FONT SIZE=3D2 FACE=3D"Arial">Can we NFS mount at /usr/user - (i.e. = >just before /var)?? My concern is that we don't end up in an = >endless loop of links.</FONT></P> > ><P><FONT SIZE=3D2 FACE=3D"Arial">Thank you.</FONT> ><BR><FONT SIZE=3D2 FACE=3D"Arial">Nancy</FONT> ></P> > ><P><B><I><FONT SIZE=3D2 FACE=3D"Arial">Nancy J. Selover</FONT></I></B> ><BR><I><FONT SIZE=3D2 FACE=3D"Arial">Asst. State = >Climatologist</FONT></I> ><BR><FONT SIZE=3D2 FACE=3D"Arial">Office of = >Climatology = >tel: 480-965-0580</FONT> ><BR><FONT SIZE=3D2 FACE=3D"Arial">Arizona State = >University fax: 480-965-1473</FONT> ><BR><FONT SIZE=3D2 FACE=3D"Arial">Tempe, AZ = >85287-1508 e-mail: address@hidden</FONT> ></P> > ></BODY> ></HTML>= > >--Boundary_(ID_eWmIL93DXqHsm9zbXDoxoA)-- >
- Prev by Date: 20021030: NFS mounting point for Gempak - re sat pointers
- Next by Date: 20021104: point NMAP/NMAP2 to my data
- Previous by thread: 20021030: NFS mounting point for Gempak - re sat pointers
- Next by thread: 20021104: point NMAP/NMAP2 to my data
- Index(es):