If you examine the code here: https://github.com/dramninjasUMD/marss.utils/blob/master/create_checkpoints.py#L46
you can see that the parsec_roi_list functions use the parsecmgmt to launch simulations instead of manually passing in arguments (like the parsec_list ones do). This means that if you just use that list instead, you'll get *all* the parsec runs without having to know the actual parameters. I'd venture to guess that the reason these two are not in parsec_list is because they require input files to be unpacked before running, and so it's not as simple as just giving some parameter string. However, if you use the parsec_roi_list, the parsecmgmt script will unpack these before launching the simulation. The other benefit of using the ROI list is that you don't have to simulate all the application startup stuff that's generally sort of useless. Hope that makes sense, Paul On Tue, Oct 23, 2012 at 3:28 PM, Mehrtash Manoochehri <[email protected]>wrote: > Hi Paul, > Thanks for your answer. As you see in the code you mention for PARSEC > suite, there are codes of 11 benchmarks and facesim and raytrace are > missing. I mean in the following section. > > parsec_list = [ > {'name' : 'blackscholes', > 'command' : > '''cd parsec-2.1 > source env.sh > > It does not make the checkpoint for these two benchmarks as they are not > specified in the code. If I want to do it by adding code manually I don't > know the parameter which are used and shown for example in Blue in the > following. > > cd /root/parsec-2.1/pkgs/apps/ferret/run > export > LD_LIBRARY_PATH=/root/parsec-2.1/pkgs/libs/hooks/inst/amd64-linux.gcc-hooks/lib > export PARSEC_CPU_NUM=`grep processor /proc/cpuinfo | wc -l`; echo > $PARSEC_CPU_NUM > ~/create_checkpoint ferret; > /root/parsec-2.1/pkgs/apps/ferret/inst/amd64-linux.gcc-hooks/bin/ferret* > corel lsh queries 10 20* %d output.txt; ~/stop_sim > > > > On Tue, Oct 23, 2012 at 12:10 PM, Paul Rosenfeld <[email protected]>wrote: > >> When you set the 'check_list' variable (here: >> https://github.com/dramninjasUMD/marss.utils/blob/master/create_checkpoints.py#L390), >> are you setting it to parsec_list or parsec_roi_list? If you use the >> region of interest hooks (i.e., parsec_roi_list), you should get all of the >> checkpoints I think. >> >> >> >> -Paul >> >> On Tue, Oct 23, 2012 at 1:54 PM, Mehrtash Manoochehri >> <[email protected]>wrote: >> >>> Hi >>> I notices that create_checkpoint.py just makes checkpoint for 11 parsec >>> benchmarks (not 13) and the code to create facesim and raytrace is not >>> written. Does anyone know the parameters which should be added there to run >>> them? >>> >>> -- >>> Regards, >>> Mehrtash Manoochehri >>> Ph.D. Student of Electrical Engineering Department, USC >>> http://www-scf.usc.edu/~mmanooch/ >>> >>> _______________________________________________ >>> http://www.marss86.org >>> Marss86-Devel mailing list >>> [email protected] >>> https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel >>> >>> >> > > > -- > Regards, > Mehrtash Manoochehri > Ph.D. Student of Electrical Engineering Department, USC > http://www-scf.usc.edu/~mmanooch/ >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
