[MITgcm-devel] llc90 set-up
Manfredi Manizza
mmanizza at ocean.mit.edu
Thu Jan 24 22:01:11 EST 2013
Hi again,
I erased the new code tree and restarted the procedure from
scratch, no error now, all fine...
Nontheless, I need now the forcing files CORE2 form Partick and Gael
for setting up the interannual runs on Pleaides.
Cheers
Manfredi
On Thu, 24 Jan 2013, Manfredi Manizza wrote:
>
> Hi,
>
> I am trying to set-up the new llc90 config from Gael
> following the readme file here below.
>
> I have problem :
>
> After this command of STEP 2 :
>
>> source ./setup_these_exps.csh
>
> I have got this :
>
> mkdir: cannot create directory `global_oce_tmp_download': File exists
> cvs checkout: No CVSROOT specified! Please use the `-d' option
> cvs [checkout aborted]: or set the CVSROOT environment variable.
> cvs checkout: No CVSROOT specified! Please use the `-d' option
> cvs [checkout aborted]: or set the CVSROOT environment variable.
> mv: cannot stat `MITgcm_contrib/gael/verification/global_oce_cs32': No such
> file or directory
> mv: cannot stat `MITgcm_contrib/gael/verification/global_oce_llc90': No such
> file or directory
> --2013-01-24 16:47:53--
> http://mitgcm.org/~gforget/global_oce_input_fields.tar.gz
>
> then I managed to downlaod only the forcing files
>
> So the two folders global_oce_cs32 and global_oce_llc90 (correct ??) are not
> created...
>
>
> I do not understad the message on the -d option. Does it refer to CVS at the
> beinning when I download the entire tree code ?
>
> Can somebody help me with that ?
>
> I hope I did not say something too naive...
>
> Thanks in advance
> Manfredi
>
> ---------------------------------------------------------------
> A) setup the experiments (incl. llc90 and cs32 core2.cnyf runs)
> ---------------------------------------------------------------
>
> 0) get MITgcm as explained @ http://mitgcm.org/public/source_code.html
> 1) the following assumes that you are in directory MITgcm/verification/
> i.e., after checkout of the model repository, do:
> cd MITgcm/verification/
> from here, get the MITgcm_contrib/gael/verification/setup_these_exps.csh
> c-shell setup script e.g. by typing
> cvs co MITgcm_contrib/gael/verification/setup_these_exps.csh
> mv MITgcm_contrib/gael/verification/setup_these_exps.csh .
> Unless you already had something in MITgcm_contrib you may want
> to remove that directory. Hereafter we wont need it anymore.
> 2) execute the setup script by typing
> source ./setup_these_exps.csh
> A pre-requisite is that you are logged in to the MITgcm
> cvs server. If you completed step1, you indeed already are.
> If otherwise, see http://mitgcm.org/public/source_code.html
> 3) step2 creates a directory global_oce_tmp_download that
> contains the experiments directories. Move them (incl.
> global_oce_input_fields) to MITgcm/verification and cd to
> that location. Once you have done this succesfully you may want
> to remove global_oce_tmp_download. We wont need it anymore.
> 4) exectute MITgcm with testreport. Two examples from one machine.
> To run the cs32 test on one cpu :
> ./testreport -t global_oce_cs32
> And to run the llc90 test on 12 cpus, using mpi
> ./testreport -match 6 -of=../tools/build_options/linux_amd64_gfortran
> -MPI 12 -command 'mpirun -np TR_NP
> ROC ./mitgcmuv' -t global_oce_llc90
> The optfile may be swaped for one that better suits your machine.
> 5) for llc90 experiment testreport should show something like
> Y Y Y Y> 6<16 16 12 12 16 16 13 11 12 11 11 11 12 13 10 11 . . pass
> global_oce_llc90
> Y Y Y N .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . . N/O
> global_oce_llc90.core2
> Y Y Y N .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . . N/O
> global_oce_llc90.ecco_v4
> Y Y Y N .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . . N/O
> global_oce_llc90.ecmwf
> implying that the main experiment ran as expected in global_oce_llc90/run.
> In contrast
> the sub-experiments, by default, fail by omission of surface forcing
> fields. This
> omission saves disk space and download time. In case you want to run the
> sub-experiments,
> you will need to obtain additional inputs. Contact us about this if
> applies.
>
>
>
>
> Manfredi
>
>
>
>
>
>
>
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel
>
More information about the MITgcm-devel
mailing list