These seem to be generated by the unit tests, according to Johannes.
ilmar
Ilmar Wilbers wrote:
> [EMAIL PROTECTED]:/tmp$ less tmpmBwtCh.inp
> *MATERIAL, NAME=MAT
> *SOLID SECTION, ELSET=NONE, MATERIAL=MAT
>
> I don't know this file format...
>
> ilmar
>
> Joachim B Haga wrote:
>> Ilmar Wilbers <[EMAIL PROTECTED]> writes:
>>
>>> I'm actually not quite sure, probably. There are .py files and .xml
>>> files. One of the .py files typically looks like:
>>> [EMAIL PROTECTED]:/tmp$ less filezcQEji.py
>>> try:
>>> from dolfin import *
>>>
>>> mesh = Mesh("/tmp/file6OyIfl.xml")
>>> f = MeshFunction("uint", mesh, "/tmp/file6OyIfl.xml")
>>> plot(f)
>>> interactive()
>>> except:
>>> import sys
>>> sys.exit(1)
>> grep of (old) sources suggests plot/plot.cpp is to blame. It generates a
>> python
>> script fileXXX.py and data file fileXXX.xml, then runs the .py.
>>
>> The generated .py could (should) clean up by removing the .xml and itself
>> before finishing:
>>
>> + fprintf(script_file, "exitcode = 0\n");
>> fprintf(script_file, "try:\n");
>> fprintf(script_file, " from dolfin import *\n\n");
>> ...
>> fprintf(script_file, " interactive()\n");
>> fprintf(script_file, "except:\n");
>> - fprintf(script_file, " import sys\n");
>> - fprintf(script_file, " sys.exit(1)\n");
>> + fprintf(script_file, " exitcode = 1\n");
>> + fprintf(script_file, "import os, sys\n");
>> + fprintf(script_file, "os.remove('%s')\n", data_name.c_str());
>> + fprintf(script_file, "os.remove('%s')\n", script_name.c_str());
>> + fprintf(script_file, "sys.exit(exitcode)\n");
>>
>>
>> I don't know about the tmpXXX.inp files, they don't seem to be generated by
>> dolfin and are not world-readable on potassium so I don't know what they
>> contain. Maybe something generated by the build tools, scons or swig perhaps?
>>
>> -j.
>>
>> _______________________________________________
>> DOLFIN-dev mailing list
>> [email protected]
>> http://www.fenics.org/mailman/listinfo/dolfin-dev
> _______________________________________________
> DOLFIN-dev mailing list
> [email protected]
> http://www.fenics.org/mailman/listinfo/dolfin-dev
_______________________________________________
DOLFIN-dev mailing list
[email protected]
http://www.fenics.org/mailman/listinfo/dolfin-dev
