Hi Bibek,
The Chapel implementation of miniMD is based on the mantevo reference version
which can be downloaded here (I think this is still the right location):
https://mantevo.org/download
The reference version comes with a number of sample input files, and I believe
the default is "in.lj.miniMD".
If I recall correctly, when the Chapel version was being merged into the source
tree there was some concern over whether or not we could include the input
files and stay compatible with licensing. We opted to leave the input files out
of the source tree, and I don't think we've revisited the issue since then.
In our correctness and performance testing of miniMD we have been using the
runtime flag "--size N", which will generate a space filled with 'atoms'.
-Ben Harshbarger
________________________________
From: Bibek Ghimire [[email protected]]
Sent: Tuesday, September 15, 2015 6:59 PM
To: [email protected]
Subject: in.lj.miniMD
Hi everyone,
I was looking into miniMD to understand one of the benchmark application
of chapel and saw in helpers/initMD.chpl : input_file = "in.lj.miniMD".
Is in.lj.miniMD file created by chapel during runtime? because I could not
find this file in the folder. If it not create how does chapel provide this
file?
-Bibek
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Chapel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-users
