[gembud] FW: Segmentation fault using gdedit

[Arthur A. Person]

Chris,

On Tue, 18 Mar 2008, Melick, Christopher J (UMC-Student) wrote:

>
> Is the rebuild a special process?  Is there something different I need 
> to do in order to incorporate these changes?

These parameters are used by codes throughout the package, so you need to 
rebuild the whole thing.  If you're using a stock package without many 
changes, I'd just unpack it from the tarball and rebuild from scratch 
after making the parameter changes.  That's the cleanest way to do it. 
If you didn't build it previously, I'd have whoever built your original 
package give you a hand.


                                Art


> Thank you Art and all for your help.
>
> Regards,
> Chris
>
> ________________________________
>
> From: Arthur A. Person [mailto:person at meteo.psu.edu]
> Sent: Tue 3/18/2008 10:36 AM
> To: Melick, Christopher J (UMC-Student)
> Cc: gembud at unidata.ucar.edu
> Subject: Re: [gembud] FW: Segmentation fault using gdedit
>
>
>
> Christopher,
>
> On Tue, 18 Mar 2008, Melick, Christopher J (UMC-Student) wrote:
>
>> Dear gembud users,
>>
>> I don't want to take up all of Patrick's time.  This is really for
>> anyone that might be able to help.  I still have this feeling it might
>> be the LLMXTG parameter, currently set at 9 million in GEMPAK 5.11.1.
>> My grid size is over 17 million grid points.  Could someone take a look
>> at my attached data file?
>
> Yep, that's big.  I tried a gdcfil with those dimensions on our system
> (which I've already increased the size on) and it says:
>
>    "WARNING: This grid is too large for GEMPAK programs."
>
> I assume that means you'll need to rebuild gempak with larger parameter
> values as you suspect.  When I do mine, I change the following parameters
> whereever they occur in gemprm.h, MCHPRM.Linux and GEMPRM.PRM:
>
> LLMXGD=20000000
> LLMDGG=80000000  -> 4 X LLMXGD
> LLMXTG=20000000
>
> I set the above values to 20,000,000 thinking that will allow your
> 19,000,000 grid size... you might want to make it even a little bigger.
> I'm not an expert at this... so if anyone sees a problem with the above,
> please chime in!
>
> Hope that helps...
>
>                               Art
>
>
>> Thanks you again,
>>
>> Christopher J. Melick
>>
>>
>>
>> ________________________________
>>
>> From: Melick, Christopher J (UMC-Student)
>> Sent: Mon 3/17/2008 5:44 PM
>> To: patrick
>> Subject: RE: [gembud] Segmentation fault using gdedit
>>
>>
>> Patrick,
>>
>> Thank you for your assistance.  I have imported many text files to GEMPAK before but for some reason this particular one is not working.  I keep getting the same "Segmentation Fault" no matter how much I mess with the structure.  Here is my data file.  Do you mind taking a look at my header information?
>>
>> Thank you much,
>>
>> Christopher J. Melick
>>
>> ________________________________
>>
>> From: patrick [mailto:patrick at hamweather.com]
>> Sent: Mon 3/17/2008 2:48 PM
>> To: Melick, Christopher J (UMC-Student); gembud at unidata.ucar.edu
>> Subject: Re: [gembud] Segmentation fault using gdedit
>>
>>
>>
>>> What might cause a "Segmentation Fault" while using GDEDIT
>>> to import a dataset into a GEMPAK file?  Does it have something
>>> to do with my large grid size of 5976*3284 (over 19 million grid points)?
>>
>> no.
>>
>> most likely improper header information... note the following:
>>
>> http://www.unidata.ucar.edu/cgi-bin/gempak/manual/programs_index?gdedit
>>
>> cheers,
>>
>> --patrick
>>
>>
>>
>>
>
> Arthur A. Person
> Research Assistant, System Administrator
> Penn State Department of Meteorology
> email:  person at meteo.psu.edu, phone:  814-863-1563
>
>
>

Arthur A. Person
Research Assistant, System Administrator
Penn State Department of Meteorology
email:  person at meteo.psu.edu, phone:  814-863-1563