I agree with Shantenu, you shouldn't have to debug these issues. Just send them to the list where there are a lot of people who can provide answers.
In this particular case, I think the error message is badly formatted. The command wants to be issued from inside the Cactus directory. It looks like there used to be a more useful error message in simlib.py in the GetDirSuffix routine, but it was commented out. I'm not sure why. Should we put it back?
Cheers, Steve
On 03/28/2012 10:49 PM, Sharath Maddineni wrote:
Hello Dr. Steve,
the cactus simulation build is so flaky/inconsistant
please see the following commands. This does not make senese at all to me. I have spending lot of time debugging these kind of issues. Other than these minor issues running/steps from there DARE part is done. been encountering these issues all along.
cactus build exists and when I create some times it does creates and some times it does not. Please let me know if I am doing anything wrong /[smaddi2@qb1 einsteintoolkit_build]$ /work/smaddi2/agent/einsteintoolkit_build/Cactus/simfactory/bin/sim --parfile=/work/smaddi2/agent/einsteintoolkit_build/Cactus/par/static_tov.par create --configuration sim static1/ /Parameter file: /work/smaddi2/agent/einsteintoolkit_build/Cactus/par/static_tov.par/ /Skeleton Created/ /Job directory: "/work/smaddi2/simulations/static1"/ /Error: Given sourcebasedir '/work/smaddi2/agent/einsteintoolkit_build' does not contain a Cactus directory/ /Aborting Simfactory./ /[smaddi2@qb1 einsteintoolkit_build]$ ls/ /Cactuscactus_installer.py einsteintoolkit.th http://einsteintoolkit.th GetComponentsGetComponents.1 GetComponents.2 GetComponents.3/ /[smaddi2@qb1 einsteintoolkit_build]$ pwd/ //work/smaddi2/agent/einsteintoolkit_build/ /[smaddi2@qb1 einsteintoolkit_build]$ ls Cactus/exe// /cactus_sim sim/
please let me know if I am doing anything wrong.
Sharath
Sharath
Simfactory supports having multiple Cactus source trees around; this is useful in many cases, e.g. if one has a production and a development tree. Therefore, Simfactory needs to know which source tree to use. You therefore have to call Simfactory from within the Cactus source tree. This is similar to other Unix commands such as make or svn.
The error message is indeed wrong; it should instead say that your current directory is not a subdirectory of the sourcebasedir. (The sourcebasedir is the directory containing the sourcedir, which is the actual Cactus directory.)
-erik
On Thu, Mar 29, 2012 at 10:35 AM, Steven R. Brandt sbrandt@cct.lsu.edu wrote:
I agree with Shantenu, you shouldn't have to debug these issues. Just send them to the list where there are a lot of people who can provide answers.
In this particular case, I think the error message is badly formatted. The command wants to be issued from inside the Cactus directory. It looks like there used to be a more useful error message in simlib.py in the GetDirSuffix routine, but it was commented out. I'm not sure why. Should we put it back?
Cheers, Steve
On 03/28/2012 10:49 PM, Sharath Maddineni wrote:
Hello Dr. Steve,
the cactus simulation build is so flaky/inconsistant
please see the following commands. This does not make senese at all to me. I have spending lot of time debugging these kind of issues. Other than these minor issues running/steps from there DARE part is done. been encountering these issues all along.
cactus build exists and when I create some times it does creates and some times it does not. Please let me know if I am doing anything wrong
[smaddi2@qb1 einsteintoolkit_build]$ /work/smaddi2/agent/einsteintoolkit_build/Cactus/simfactory/bin/sim --parfile=/work/smaddi2/agent/einsteintoolkit_build/Cactus/par/static_tov.par create --configuration sim static1 Parameter file: /work/smaddi2/agent/einsteintoolkit_build/Cactus/par/static_tov.par Skeleton Created Job directory: "/work/smaddi2/simulations/static1" Error: Given sourcebasedir '/work/smaddi2/agent/einsteintoolkit_build' does not contain a Cactus directory Aborting Simfactory. [smaddi2@qb1 einsteintoolkit_build]$ ls Cactus cactus_installer.py einsteintoolkit.th GetComponents GetComponents.1 GetComponents.2 GetComponents.3 [smaddi2@qb1 einsteintoolkit_build]$ pwd /work/smaddi2/agent/einsteintoolkit_build [smaddi2@qb1 einsteintoolkit_build]$ ls Cactus/exe/ cactus_sim sim
please let me know if I am doing anything wrong.
Sharath
Users mailing list Users@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/users
Hi Erik,
Thanks for the input. working directory seems to be the issue. I changed it to /path/to/Cactus.
$sim create seems to work fine now.
Once again thanks a lot.
Sharath.
On Fri, Mar 30, 2012 at 9:29 PM, Erik Schnetter schnetter@cct.lsu.eduwrote:
Sharath
Simfactory supports having multiple Cactus source trees around; this is useful in many cases, e.g. if one has a production and a development tree. Therefore, Simfactory needs to know which source tree to use. You therefore have to call Simfactory from within the Cactus source tree. This is similar to other Unix commands such as make or svn.
The error message is indeed wrong; it should instead say that your current directory is not a subdirectory of the sourcebasedir. (The sourcebasedir is the directory containing the sourcedir, which is the actual Cactus directory.)
-erik
On Thu, Mar 29, 2012 at 10:35 AM, Steven R. Brandt sbrandt@cct.lsu.edu wrote:
I agree with Shantenu, you shouldn't have to debug these issues. Just
send
them to the list where there are a lot of people who can provide answers.
In this particular case, I think the error message is badly formatted.
The
command wants to be issued from inside the Cactus directory. It looks
like
there used to be a more useful error message in simlib.py in the GetDirSuffix routine, but it was commented out. I'm not sure why. Should
we
put it back?
Cheers, Steve
On 03/28/2012 10:49 PM, Sharath Maddineni wrote:
Hello Dr. Steve,
the cactus simulation build is so flaky/inconsistant
please see the following commands. This does not make senese at all to
me. I
have spending lot of time debugging these kind of issues. Other than
these
minor issues running/steps from there DARE part is done. been encountering these issues all along.
cactus build exists and when I create some times it does creates and some times it does not. Please let me know if I am doing anything wrong
[smaddi2@qb1 einsteintoolkit_build]$ /work/smaddi2/agent/einsteintoolkit_build/Cactus/simfactory/bin/sim
--parfile=/work/smaddi2/agent/einsteintoolkit_build/Cactus/par/static_tov.par
create --configuration sim static1 Parameter file: /work/smaddi2/agent/einsteintoolkit_build/Cactus/par/static_tov.par Skeleton Created Job directory: "/work/smaddi2/simulations/static1" Error: Given sourcebasedir '/work/smaddi2/agent/einsteintoolkit_build'
does
not contain a Cactus directory Aborting Simfactory. [smaddi2@qb1 einsteintoolkit_build]$ ls Cactus cactus_installer.py einsteintoolkit.th GetComponents GetComponents.1 GetComponents.2 GetComponents.3 [smaddi2@qb1 einsteintoolkit_build]$ pwd /work/smaddi2/agent/einsteintoolkit_build [smaddi2@qb1 einsteintoolkit_build]$ ls Cactus/exe/ cactus_sim sim
please let me know if I am doing anything wrong.
Sharath
Users mailing list Users@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/users
-- Erik Schnetter schnetter@cct.lsu.edu http://www.perimeterinstitute.ca/personal/eschnetter/
users@lists.einsteintoolkit.org
-
Erik Schnetter -
Sharath Maddineni -
Steven R. Brandt