1.2.0 new_case error -mach userdefined

[Xax]

I am trying to set up a fresh version of CESM 1.2.After downloading the code I attempt to create a new case:./create_newcase -case test01 -res f45_g37 -compset X -mach userdefined However I receive the error:Creating /home/myname/CESM/scripts/test01
env: /home/myname/CESM/scripts/ccsm_utils/Machines/mkbatch.userdefined: No such file or directory
ERROR: env CCSMUSER=myname CASE=test01 CASEROOT=/home/myname/CESM/scripts/test01 env PHASE=set_larch /home/myname/CESM/scripts/ccsm_utils/Machines/mkbatch.userdefined failed: 32512


Any ideas on how to solve this very aprecciated. I have not done any other prior configurations.

 

[Xax]

Now I am trying new_case with CESM 1.2.2 with the same results, all on my Ubuntu notebook.

 

[jedwards]

You need to read the manual and follow the instructions in chapter 5

 

[Xax]

Dear jedwards,I am following the manual: 1) downloading the code 2) changing to the scripts subdirectory and attempting ./create_newcase receiving the above errors.

 

[jedwards]

What is the full path to your scripts directory?  

 

[Xax]

/home/myname/CESM/scripts/

 

[jedwards]

Does the file /home/myname/CESM/scripts/ccsm_utils/Machines/mkbatch.userdefined exist?
If not I think you have a corrupt source tree and you should download the 1.2.2 release.

 

[Xax]

yes, the file exists. Could it be a messed up perl installation or something?
I have perlbrew installed.

 

[Xax]

I resetup a Virtual Machine within VirtualBox running a fresh Ubuntu installation with CESM1.2.2 but still receive the identical error.

 

[jedwards]

I assume that you are talking about Oracle VDI?   As far as I know CESM has never been ported to this environment andnoone here has access to a machine configured in this manor.   Perhaps you should try building CESM in a more standard environment first,learn the procedure, then go back and try your VDI. 

 

[santos]

Make sure that tcsh is installed, and that the command at the top of mkbatch.userdefined points to it (or to a link or wrapper for it). E.g. if you have this:#!/bin/csh -fMake sure that "/bin/csh" actually exists, or change this line to point to the right path.