On Wed, Aug 20, 2014 at 9:48 AM, Frank Loeffler wrote:
> On Tue, Aug 19, 2014 at 08:42:16PM -0700, Roland Haas wrote:
> > I would try and have both GRHydro and GRHydro_InitData in the same
> > repository
>
> I agree here. We should not split test thorns from the thorns they test,
> if they depend
Hi again list,
I've just done another install onto my 64-bit Ubuntu 14.04 machine (the
32-bit Debian one is running now), and when I submit a job I get this
output:
$ ./simfactory/bin/sim show-output --follow static_tov
Simulation name: static_tov
===
On 20/08/14 14:58, Frank Loeffler wrote:
> On Wed, Aug 20, 2014 at 02:53:24PM +0100, Ian Smith wrote:
>> $ cat simfactory/mdb/machines/sumo.ini
>> [generic]
>
> Change this to [sumo] - because then simfactory will know that this
> machine's name is 'sumo'.
>
>> # Access to this machine
>> hostname
On Wed, Aug 20, 2014 at 02:53:24PM +0100, Ian Smith wrote:
> $ cat simfactory/mdb/machines/sumo.ini
> [generic]
Change this to [sumo] - because then simfactory will know that this
machine's name is 'sumo'.
> # Access to this machine
> hostname= generic.some.where
> aliaspattern= ^gene
On Wed, Aug 20, 2014 at 02:47:12PM +0100, Ian Smith wrote:
> ./simfactory/bin/sim build --thornlist=manifest/einsteintoolkit.th
> --machine=simfactory/mdb/machines/sumo.ini
> Error: retrieving Machine entry for Machine
> simfactory/mdb/machines/sumo.ini: Machine
I believe that. --machine takes
I forgot to list my machine file, sorry!
$ cat simfactory/mdb/machines/sumo.ini
[generic]
# Machine description
nickname= sumo
name= Generic Machine
location= somewhere
description = Whatever
status = personal
# Access to this machine
hostname= ge
On Tue, Aug 19, 2014 at 08:42:16PM -0700, Roland Haas wrote:
> I would try and have both GRHydro and GRHydro_InitData in the same
> repository
I agree here. We should not split test thorns from the thorns they test,
if they depend on each other as closely as these two do, depending on a
case-by-ca
On 20/08/14 13:56, Dumsani Ndzinisa wrote:
> Hi Ian,
>
> As far as I know, those limits are set in the machine definition file,
> the .ini file specifically. Once you have added them on, do a fresh
> build, making sure to pass the ini file as an (optional) argument to
> you new build. That is, simf
Hi Ian,
As far as I know, those limits are set in the machine definition file,
the .ini file specifically. Once you have added them on, do a fresh
build, making sure to pass the ini file as an (optional) argument to
you new build. That is, simfactory/bin/sim build .
--machine=simfactory/mdb/
Hi Guys,
I tried to run the resource-reduced example (static_tov_small.par) in
the simplified guide, but the simulation only uses one CPU core. I
tried a couple of things to fix this:
ian@sumo Wed Aug 20 01:26 PM /opt/EinsteinToolkit/Cactus
$ ./simfactory/bin/sim submit static_tov
--parfile=p
[sorry to have to re-send this, Thunderbird is playing havoc with my
From: address!]
Hi again List,
I tried again from scratch, in case I was building against artifacts
created with incomplete dependencies (looks like I was).
I got this:
Formaline: Creating git master repository...
Formaline:
On 18/08/14 18:20, Erik Schnetter wrote:
> Ian
>
> Most likely, setting both F77 and F90 to "gfortran" will work.
Thanks for the suggestion, Erik, I tried this, and still get the same
error message.
> You didn't specify what MPI options you are using when configuring. Can
> you provide more deta
12 matches
Mail list logo