[mesa-users] Initialization Error
paxton at kitp.ucsb.edu
Wed Nov 13 12:58:10 EST 2013
Let's see if there is someone on mesa-users who has experience with getting things running on a cluster --- that's a problem that I've been careful to avoid myself!!!
If you have experience getting mesa running on a cluster, could you help Ehsan get started?
On Nov 13, 2013, at 8:04 AM, Ehsan Moravveji wrote:
> Hello Bill,
> Last week, I asked about solving the following error from the jobs that I run on a supercomputer:
> Revision: 5548
> Wed Nov 13 16:37:51 CET 2013
> failed in net_finish_def
> failed in stardata_init
> star_init ierr 5014
> init_and_alloc ierr 5014
> Wed Nov 13 16:37:53 CET 2013
> And you wrote the following:
>> It looks like it can read the standard location cache, but it can't write it.
>> If that's the case, you have 2 options:
>> 1) preload the standard cache with everything you will need before running on the compute node.
> apparently the files in e.g. /mesa/data/kap_data/cache are binary files.
> If I understood you well, I have to put the right files into this directory with .bin extension.
> For this purpose, i want to copy from my own laptop to the supercomputer.
> Is this what you mean by pre-loading?
>> 2) have a separate cache in a place that the compute node process can write.
> This did not work!
>> You can do that using these controls in star_job
>> ! cache directories
>> ! mesa uses caches to improve performance.
>> ! the default location for these is in the mesa/data directory,
>> ! but in some situations it is useful to keep the caches
>> ! separately so, for example, multiple users can share the code
>> ! and each can have a separate set of caches.
>> ! '' means use default location for cache.
>> ! The need for separate caches arises in cases where we need
>> ! to put the main mesa directory in a location that is "read only"
>> ! for a group of users (such as in a system directory that requires
>> ! "root" or "superuser" to write). In that case the caches must
>> ! be moved out of the main directory to locations that the user
>> ! can write.
>> eosDT_cache_dir = ''
>> eosPT_cache_dir = ''
>> ionization_cache_dir = ''
>> kap_cache_dir = ''
>> rates_cache_dir = ''
>> weaklib_cache_dir = ''
>> On Nov 6, 2013, at 9:33 AM, Ehsan Moravveji wrote:
>>> Because I already have MESA_DIR set in my .bashrc, I do not explicitly put mesa_dir in my star_job:
>>> $> echo $MESA_DIR
More information about the Mesa-users