[Users] Uninitialised variables

Roland Haas rhaas at illinois.edu
Thu Oct 6 10:39:59 CDT 2016

Hello Ian,

> Aha, that's interesting.  Though I guess it would probably confuse a
> lot of thorns, so I'm not sure how useful it in in practice.  The
> initial data solver would run again, for example.  
Correct. The current default is "safer" it seems. The "relaxed" setting
I have never seen used myself. 

> I would have
> expected Carpet to initialise variables to poison, so I should be
> seeing poison.
That is also what I would have expected. Have you set both
posion_new_memory and poison_new_timelevels turned on?

> What I am doing now is initialising the thorn in
> basegrid, and checking an "initialised" Cactus variable.  If this is
> 1, then I don't do anything.  If it's anything other than 1 (poison,
> zero, etc) then I assume the thorn has never been initialised.  This
> is probably not an approved, elegant solution, but I expect it will
> work.
Well it's kind of what you have to do. You should be able to just
initialize in basegrid all the time, since the basegrid values will be
overwritten during checkpoint recovery as far as I remember.


My email is as private as my paper mail. I therefore support encrypting
and signing email messages. Get my PGP key from http://keys.gnupg.net.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 163 bytes
Desc: OpenPGP digital signature
Url : http://lists.einsteintoolkit.org/pipermail/users/attachments/20161006/5e841d44/attachment.bin 

More information about the Users mailing list