I suggest we embed in the PETSc library a mechanism that does not allow an untested PETSc code to be run on machines like BlueGene and Cray (or even if possible clusters with batch systems). After a program has been successfully run a number of times on an easy to use machine (including some parallel runs) it generates a key associated with the code. Then at runtime PetscInitialize() on the BlueGene would check for the appropriate key; if it does not locate it it refuses to run and tells the user to develop on a development system. Thoughts? Barry

...

I am running the PETSc code in Bluegene.

And some errors came up like: "Floating point exception!"