+- jeplus.org forums (http://jeplus.org/mybb)
+-- Forum: Building simulation tools (http://jeplus.org/mybb/forumdisplay.php?fid=1)
+--- Forum: jEPlus (http://jeplus.org/mybb/forumdisplay.php?fid=2)
+--- Thread: problem with command line execution (solved) (/showthread.php?tid=18)
problem with command line execution (solved) - Ery Djunaedy - 11-22-2014
I have two problems with command line execution of jEPlus:
1. No matter what I said in the number of jobs (I specified 6), jEPlus always run to the maximum number of processors in my computer (8). This only happens through command line. The GUI seems to make jEPlus honor the limit.
2. It always run readvarseso even if I have unselected the RVI. This process alone can take 45 mins (for a total 384 jobs), so I would like to avoid this if possible.
Does this only happen to my computer? I am running on Ubuntu.
Thanks!
RE: problem with command line execution - Yi - 11-22-2014
Hi Ery, when running from command line you control the number of threads (processor cores) used for simulation with the argument -local. In your case, it should be "-local 6". To the second question, if you don't want any result in the CSV output, put
eplusout.abc
eplusout.csv
0
in the RVI file, it will stop ReadVars extracting results.
Yi
RE: problem with command line execution - Ery Djunaedy - 11-22-2014
Thanks Yi!
RE: problem with command line execution - Ery Djunaedy - 11-24-2014
Well, a new issue came up. When I set the RVI file like you suggested above, I got an error like below. I copied the last job, and then an error with jEPlus is collecting results. All the jobs are completed OK. The only problem is that the process stalled right there, so if I have a script to call another batch of jobs, it will not be executed. Any thoughts on this?
Thanks
Ery
*********************************
2014-11-24 11:38:18,216 INFO [Thread-385] agent.EPlusAgent ( ) - Job EP_G-T_0-W_0-P1_5-P2_1-P3_3-P4_3-P5_1 started. 0 more to go!
2014-11-24 11:38:18,418 INFO [Thread-385] agent.EPlusAgent ( ) - Nearly there ...
2014-11-24 11:40:42,454 INFO [Thread-385] agent.EPlusAgent ( ) - Local batch simulation controller is FINISHED [Que=0, Run=0, Fin=384]
2014-11-24 11:40:42,455 INFO [Thread-385] agent.EPlusAgent ( ) - Local agent stopped.
2014-11-24 11:40:42,455 INFO [Thread-385] agent.EPlusAgent ( ) - Collecting results ...
2014-11-24 11:40:43,257 INFO [Thread-385] agent.EPlusAgent ( ) - Standard RVI result collector collected 384 simulation reports in /opt/simulations/jEPlus_v1.5_beta_07/parametrics2/2015_steelframe_conditioned/output/RunTimes.csv
2014-11-24 11:40:43,272 INFO [Thread-385] agent.EPlusAgent ( ) - Standard RVI result collector collected job index table in /opt/simulations/jEPlus_v1.5_beta_07/parametrics2/2015_steelframe_conditioned/output/SimJobIndex.csv
Exception in thread "Thread-385" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2219)
at java.util.ArrayList.grow(ArrayList.java:242)
at java.util.ArrayList.ensureExplicitCapacity(ArrayList.java:216)
at java.util.ArrayList.ensureCapacityInternal(ArrayList.java:208)
at java.util.ArrayList.add(ArrayList.java:440)
at java.lang.String.split(String.java:2288)
at java.lang.String.split(String.java:2355)
at jeplus.postproc.EPlusRVIReader.readResult(EPlusRVIReader.java:122)
at jeplus.postproc.EPlusRVIReader.readResult(EPlusRVIReader.java:77)
at jeplus.postproc.EsoResultCollector.collectResutls(EsoResultCollector.java:75)
at jeplus.agent.EPlusAgent.runResultCollection(EPlusAgent.java:401)
at jeplus.agent.EPlusAgentLocal.run(EPlusAgentLocal.java:213)
at java.lang.Thread.run(Thread.java:745)
RE: problem with command line execution - Ery Djunaedy - 11-24-2014
Nevermind, I missed the extension .abc in your example of RVI file. Yes, when I make it to refer to unknown file, then it works, i.e. readvarseso does not start and there is no error.
RE: problem with command line execution - Yi - 11-24-2014
Yes, this is a hack and is probably not the best way to do things. A better way would be to use the new .rvx file in v1.5 beta7, in which the rvi processes can be individually specified. In this case if you don't specify any rvi, jEPlus will not run ReadVarsEso.
An empty .rvx looks like this:
Code:
{ "notes" : "This is an empty RVX",
"rvis" : [ ],
"sqls" : [ ],
"scripts" : [ ]
}Save it as my.rvx and assign it to the project; it should also solve your problem.
Yi