Hi Andy, I think it must be something with MPI4PY on my Mac. I got it to compile and run on the Utility server here at ERDC.
Now, is the example here https://github.com/acbauer/CatalystExampleCode/tree/master/CxxMultiPieceExample the easiest way to incorporate extents into the Fortran code? I am basically trying to run the Fortran example on more than one processor and I was going to adapt the Fortran FXCxxAdaptor following the CxxMultiPieceExample. Unless there is a better way. My first attempt didn't create the expanding ball that the serial Fortran example does. It did produce an image, but not the one that I wanted. Thanks Lucas ________________________________ From: Andy Bauer [[email protected]] Sent: Tuesday, April 30, 2013 9:28 PM To: Pettey . Lucas Cc: [email protected] Subject: Re: [Paraview] Initialize coprocessor fails Hi Lucas, Every process should call coprocessorinitializewithpython(). I'm not sure how to solve this but first off maybe trying the Fortran 90 example at https://github.com/acbauer/CatalystExampleCode may help simplify the problem. What machine are you trying this on and what version of ParaView are you using? Andy On Mon, Apr 29, 2013 at 4:25 PM, Pettey . Lucas <[email protected]<mailto:[email protected]>> wrote: Hello! I have a Fortran serial test case working that uses the Catalyst coprocessor to generate images. I tried moving to a parallel test case, but the program crashes with the error: ORTE_ERROR_LOG: Attempt to redefine an existing data type in file runtime/orte_globals.c at line 218 at the call to initialize the coprocessor: call coprocessorinitializewithpython("coproc.py",9) Does this call change in parallel, or should only one processor be calling it? If I comment out the line of code that calls the coprocessor initialization, then the code runs fine, I just get the error that the co-processor needs to initialize every time there is a VTK coprocessor call. Thanks for any help, Lucas ________________________________ This electronic message transmission and any attachments that accompany it contain information from DRC® (Dynamics Research Corporation) or its subsidiaries, or the intended recipient, which is privileged, proprietary, business confidential, or otherwise protected from disclosure and is the exclusive property of DRC and/or the intended recipient. The information in this email is solely intended for the use of the individual or entity that is the intended recipient. If you are not the intended recipient, any use, dissemination, distribution, retention, or copying of this communication, attachments, or substance is prohibited. If you have received this electronic transmission in error, please immediately reply to the author via email that you received the message by mistake and also promptly and permanently delete this message and all copies of this email and any attachments. We thank you for your assistance and apologize for any inconvenience. _______________________________________________ Powered by www.kitware.com<http://www.kitware.com> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
