Re: [Paraview] Attempting to run Catalyst CFullExample
Hi Bill, Good news! You now get the same error that I do when you try to run the examples scripts. This means that everything is installed correctly. Notice that the trace back error is related to 'vtkCPPythonHelper' in the sample script. This would indicate that the script you are using is incompatible with ParaView 4.0. With ParaView 4.0, you should get the same results (or in this case error) in serial and parallel. It seems that Catalyst based on ParaView 4.0 is better at determining whether or not to use parallel functions. There is probably a more detailed explanation, but from my observations it is smarter. To get this example working with 4.0, we need a sample pipeline from which we can export the state. If you look in FEDataStructures.c, you will see what the code is doing. The code creates a 3D CoRectilinear grid in the grid struc. A second struc called Attributes assigns Velocities as point data and Pressure as cell data. As written, the velocity varies in time and the y direction only, while pressure is constant at zero. A good exercise is to write the data to a file using your favorite method to get it into ParaView. For small data like this, I like to run it on a single processor and use the RAW (binary) data format. I would recommend just working with the velocity since it is point based and is the only variable doing anything interesting. Once you have done that, create whatever filter you like in the pipeline. The example script contains a Slice filter. If you want to be able to manipulate the data after co-processing, make sure you attach a writer to the end of the pipeline. If you don't have a writer, you can ask ParaView to output images or set up live visualization. This is done through the Co-Processing - Export State option. If you don't want to go through all of this, you have 2 options. The first is to wait until Andy updates the examples to work with ParaView 4.0. The second would be to checkout the version from 5-14: http://paraview.org/gitweb?p=ParaView.git;a=commit;h=6720c3dc175bea3e0098c2769537d174d989. I THINK this version aligned Catalyst with the VTK changes and was a working version. I did a lot of rebuilding around this time, so I can't be sure. I have been working with Catalyst and Fortran and use my own scripts exclusively. This is a learning process, so if you are learning, you are marching towards the finish line. The code was in flux for a while, but seems to be stable now. I hope this helps you continue to move forward. Lucas From: Bill Sherman [sherm...@indiana.edu] Sent: Wednesday, May 29, 2013 10:36 AM To: Pettey . Lucas; ParaView list Cc: Bill Sherman Subject: Re: [Paraview] Attempting to run Catalyst CFullExample Hello again Lucas (and ParaView community), I just wanted to explain why the program runs for a moment and then returns the prompt if you did not provide the script as an argument like you described in your first email. Providing the script as an argument is the correct way to execute the program. Since you didn't get any errors running the program without the script, the C portion of the program is OK. Okay. I'm not quite sure what you mean by ParaView versions of the python script. What I mean is that the version of ParaView which generated the script must be the same as the version of ParaView that you are running and using in your compiler. I think Andy was using the latest git version of ParaView in generating his scripts. So, if his examples are dated May 13, a version of ParaView around that date would be better to use. Yours is a clone in April and a lot of work was being done around then for Catalyst. I have been working on Fortran versions and I know I had to download and rebuild ParaView quite frequently. Make sense. I do know the latest git clone does not work with those scripts because the repository has been updated to 4.0, as that is what I have and I tried it. Okay, yesterday I downloaded and compiled a git clone (which calls itself 4.0.0 RC-2. I would first try to export a script from your version of ParaView. Make sure the CoProcessing plugin is loaded and then you should be able to export the state. You will need to modify the code to write the data to an output file and then open that in ParaView and create a pipeline that you want the CoProcessor to generate. You can then export the state through the plugin. This will generate a python script that you can use in place of the sample provided. That would be good if there were a step-by-step tutorial that goes with the examples, but I know that time (especially with the 4.0 release preparations) is tight. But w/o step-by-step, or at least a picture of what the pipeline is supposed to look like, I'm not ready to be able to figure out how to build the pipeline to match the example code. If that doesn't work, then you may might to rebuild to the latest
Re: [Paraview] Attempting to run Catalyst CFullExample
Hi Bill, I did provide the script as an argument (following the instructions at the top of the python script). I just wanted to explain why the program runs for a moment and then returns the prompt if you did not provide the script as an argument like you described in your first email. Providing the script as an argument is the correct way to execute the program. Since you didn't get any errors running the program without the script, the C portion of the program is OK. I'm not quite sure what you mean by ParaView versions of the python script. What I mean is that the version of ParaView which generated the script must be the same as the version of ParaView that you are running and using in your compiler. I think Andy was using the latest git version of ParaView in generating his scripts. So, if his examples are dated May 13, a version of ParaView around that date would be better to use. Yours is a clone in April and a lot of work was being done around then for Catalyst. I have been working on Fortran versions and I know I had to download and rebuild ParaView quite frequently. I do know the latest git clone does not work with those scripts because the repository has been updated to 4.0, as that is what I have and I tried it. I would first try to export a script from your version of ParaView. Make sure the CoProcessing plugin is loaded and then you should be able to export the state. You will need to modify the code to write the data to an output file and then open that in ParaView and create a pipeline that you want the CoProcessor to generate. You can then export the state through the plugin. This will generate a python script that you can use in place of the sample provided. If that doesn't work, then you may might to rebuild to the latest ParaView and try exporting a script from that version. It is critical that the ParaView version used to generate the script is the same as the ParaView version used to compile the program. Andy will probably have some good suggestions as he is the primary Catalyst developer. He may even update those examples to ParaView 4.0 soon. Also, these are all parallel examples so make sure you are using the correct mpiexec syntax. I know that was something I didn't realize the first time I tried these examples. Hope this clarifies some thing, Lucas From: William Sherman [sherm...@indiana.edu] Sent: Monday, May 27, 2013 12:34 AM To: Pettey . Lucas Cc: ParaView list; William Sherman Subject: Re: [Paraview] Attempting to run Catalyst CFullExample Hello again, The Catalyst C and C++ examples all require the python script as an argument at run time. The Fortran example requires that the script be in the same directory. So when you aren't giving the script as an argument, the code is running but doesn't have any information about what to co-process, and it exits doing nothing. I did provide the script as an argument (following the instructions at the top of the python script). As for the seg fault, my guess is that the ParaView versions of the python script and the one against which you are compiling are different. I know they are different on mine and while I don't get a seg fault, I get some errors about the VTK class structures. I'm not quite sure what you mean by ParaView versions of the python script. I do know that when I compiled the simulation with the Catalyst code, I am pointing to the same version of ParaView that I'm running. I don't know how that correlates to python versions. I would recommend also checking out the latest versions of the examples. Andy has done a lot of work on them recently, so if they are even a few weeks old, they might not work as expected. Also, you could just export a new script with the PV version built on your system. Well, thought I was downloading his latest examples by grabbing them directly from his github page. Is there somewhere else to look for them? Most of the files are dated May 13, 2013. I hope this points you in the right direction. Not yet, but if you could explain what you mean by the ParaView python version, that might shed some light. I know I'm using the same version of ParaView. Lucas Pettey Thanks for the suggestions, Bill From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf of Bill Sherman [sherm...@indiana.edu] Sent: Friday, May 24, 2013 6:56 PM To: ParaView list Cc: Bill Sherman Subject: [Paraview] Attempting to run Catalyst CFullExample Hello, I'm in the process of attempting to learn how to use the Catalyst feature of ParaView, and I have a problem. I found the sample code on github: - https://github.com/acbauer/CatalystExampleCode and I began by compiling the CFullExample application. There is some weirdness when trying to compile the application as a non-Catalyst simulation, but since I'm trying
Re: [Paraview] Attempting to run Catalyst CFullExample
Hi Bill, The Catalyst C and C++ examples all require the python script as an argument at run time. The Fortran example requires that the script be in the same directory. So when you aren't giving the script as an argument, the code is running but doesn't have any information about what to co-process, and it exits doing nothing. As for the seg fault, my guess is that the ParaView versions of the python script and the one against which you are compiling are different. I know they are different on mine and while I don't get a seg fault, I get some errors about the VTK class structures. I would recommend also checking out the latest versions of the examples. Andy has done a lot of work on them recently, so if they are even a few weeks old, they might not work as expected. Also, you could just export a new script with the PV version built on your system. I hope this points you in the right direction. Lucas Pettey From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf of Bill Sherman [sherm...@indiana.edu] Sent: Friday, May 24, 2013 6:56 PM To: ParaView list Cc: Bill Sherman Subject: [Paraview] Attempting to run Catalyst CFullExample Hello, I'm in the process of attempting to learn how to use the Catalyst feature of ParaView, and I have a problem. I found the sample code on github: - https://github.com/acbauer/CatalystExampleCode and I began by compiling the CFullExample application. There is some weirdness when trying to compile the application as a non-Catalyst simulation, but since I'm trying to learn Catalyst, that's just an aside to the code maintainers. So I have the application (FEDriver) compiled, and there is a sample python script. I ran ParaView (same version as I used when compiling FEDriver -- a git clone from April), and I start the Catalyst connection: - Tools - Connect to Catalyst (which I had to find by poking around, the SC'12 Catalyst tutorial doesn't seem to mention this -- or not that I noticed. An aside to the code documenters.) So I followed the instructions in the python script, and with ParaView accepting Catalyst connections on port 2, this is what happens: % ./FEDriver SampleScripts/feslicescript.py Segmentation fault (core dumped) Actually, that happens regardless of whether ParaView is running or not, but it only happens when I give the python script as an argument -- w/o the script, it runs for a moment and then returns to the prompt. So what am I missing? Thanks, Bill -- Bill Sherman Sr. Technology Advisor Advanced Visualization Lab Pervasive Technology Inst Indiana University sherm...@indiana.edu ___ 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 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 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
[Paraview] Scalar components and Python Calculator
Hello, I am trying to use the Python Calculator on 2 different Scalar components in the same data file. I have written the real and imaginary parts of a Fortran complex data type to a single .raw binary file. ParaView correctly opens this file when I tell it that there are 2 scalar components. I can use the Calculator to perform calculations on the X and Y components (the real gets imported by default as ImageData_X and the imaginary as ImageData_Y). An expression in the Calculator filter such as: sqrt(ImageData_X^2 + ImageData_Y^2) works fine. The Python Calculator, however, generates an error that ImageData_X and ImageData_Y are not defined. Both filters are set to Point Data. Any suggestions? Thanks 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 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
[Paraview] Catalyst CxxFullExample Seg Faults
Hello, I get a segmentation fault trying to run the CxxFullExample on the Utility Server here at ERDC. I have successfully run the serial Fortran examples using the same build of ParaView. Thanks, 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 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
Re: [Paraview] Initialize coprocessor fails
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 [andy.ba...@kitware.com] Sent: Tuesday, April 30, 2013 9:28 PM To: Pettey . Lucas Cc: paraview@paraview.org 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 lpet...@drc.commailto:lpet...@drc.com 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.comhttp://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
[Paraview] Initialize coprocessor fails
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 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
Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
Hi Andy, I do not mind at all. In fact, I am quite happy to have contributed something given all the help that you have provided to us. Thanks, Lucas From: Andy Bauer [andy.ba...@kitware.com] Sent: Wednesday, March 27, 2013 3:31 PM To: paraview@paraview.org; Pettey . Lucas Subject: Re: CoProcessing with Fortran and ParaView 3.98 Hi Lucas, Do you mind if I use the coproc files you sent me as an example for Catalyst? Thanks, Andy On Tue, Mar 26, 2013 at 3:29 PM, Andy Bauer andy.ba...@kitware.commailto:andy.ba...@kitware.com wrote: Hi Lucas, I was able to replicate your issue on the mac. There is a fix for it that is waiting a code review and dashboard feedback. I'll let you know when it's in the main ParaView repo (which should be a couple of days). Andy On Mon, Mar 25, 2013 at 5:56 PM, Andy Bauer andy.ba...@kitware.commailto:andy.ba...@kitware.com wrote: Hi Lucas, I'm getting rid of the history as it was getting really long and making it hard to read. There is a bug with the vtkMPIImageReader -- http://paraview.org/Bug/view.php?id=13968. I think it should be fixed in a couple of days. I'm not getting the issues with the script that was in the tarball on my linux machine but I'll try it on a Mac. I did have to have the python script in the directory I was working in (a relative path to it didn't work when I tried to run ./CoProcessingExample ../coproc.py). Andy === Hi Andy, So I got the repo version of ParaView built on both my Mac laptop (10.7.5) and Mac desktop (10.8.3). The CoProc code from the tar file you sent compiles just fine on both machines. On execution, both machines generate the error: lucass-mac-pro:coprocf90 lucaspettey$ ./CoProcessingExample Traceback (most recent call last): File string, line 2, in module File /Users/lucaspettey/codes/BEC/ coproc.py, line 9, in module import vtkCoProcessorPython ImportError: No module named vtkCoProcessorPython Traceback (most recent call last): File string, line 2, in module So I thought that I would remake the images and generate a new coprocessing script. The second problem is that ParaView crashes when it tries to open .RAW files on either machine. I get the following error when I select the file: ERROR in .../vtkSIProxy.cxx line 307 vtkSISourceProxy: failed to create vtkMPIImageReader XDMF and other file types seem to open ok. These files opened fine under the release version of ParaView. Thanks, 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 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
[Paraview] Latest Git repository issues
Hello, I have been working with Andy on some CoProcessing issues and need to pull from the repository. I did this Friday with no issues, but I wanted to check out a fresh copy today. When I did, I got an error in CMake that it could not find VTK. It seems the VTK directory is empty that comes with the repository. All of the submodules seem to be empty. I tried: git submodule init git submodule foreach git pull origin master These tell me I am up to date even though the submodule directories are empty. the .gitmodules file does appear to have the correct git addresses for each submodule. Any suggestions are appreciated. Thanks, 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 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
Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
Hi Andy, I have attached a tar file with all 3 source code files, the Python script and the CMakeLists.txt file used to build the executable. Thanks so much for helping with this. Lucas From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf of Andy Bauer [andy.ba...@kitware.com] Sent: Friday, March 22, 2013 8:01 AM To: Pettey . Lucas Cc: paraview [paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Hi Lucas, Could you send me your CMakeLists.txt or your Makefile used to build this? I think I should be able to diagnose the problem fairly quickly in a debugger. Andy On Thu, Mar 21, 2013 at 4:44 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.com wrote: Also something weird that I have noted. The Initialize Helper Script line prints twice when I run the Fortran code and no print statements anywhere in my Python script execute (not even if they are at the top). When I run the C++ example located here: http://www.itk.org/Wiki/Coprocessing_example, the Initialize Helper Script only appears once and print statements in the Python script execute normally. I'm not sure if this helps or makes things worse. Thanks, Lucas From: paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org [paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org] on behalf of Pettey . Lucas [lpet...@drc.commailto:lpet...@drc.com] Sent: Thursday, March 21, 2013 3:12 PM To: Andy Bauer Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Nothing printed at all. Does anything special have to be done during the compile/link steps for the python script to work properly? Thanks, Lucas From: Andy Bauer [andy.ba...@kitware.commailto:andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 3:00 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 How about trying: psi01_.UpdatePipeline() print psi01_.GetDataInformation().DataInformation.GetNumberOfPoints() right about where the writer was created. This will give print out the number of points in the data set that you have. Andy On Thu, Mar 21, 2013 at 3:47 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com wrote: Sorry, Andy, that didn't seem to work either. Let me know what information would be useful to print. Thanks Lucas From: Andy Bauer [andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 2:36 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Hmm, how about trying replacing those two lines with: ParallelImageDataWriter1 = CreateCPWriter( XMLPImageDataWriter, fullgrid_%t.pvti, 1, cp_writers ) Let me know how that goes. If not, I think we'll need to put some print statements in there. Andy On Thu, Mar 21, 2013 at 3:31 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com wrote: Yes I did. I have attached the latest script. Thank you for your valiant efforts in trying to solve this problem. Lucas From: Andy Bauer [andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 2:22 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Did you also include the w.UpdatePipeline() part after the writer was created? It won't create the file unless that's in there. Andy On Thu, Mar 21, 2013 at 3:17 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com wrote: Hi Andy, Changing to Scalars=['POINTS','psi01'] did not change anything. I still get the same error and blank image. I tried adding the XMLPImageDataWriter command
Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
Hi Andy, Changing to Scalars=['POINTS','psi01'] did not change anything. I still get the same error and blank image. I tried adding the XMLPImageDataWriter command, but no file 'fullgrid.pvti' was produced so I can't tell what is being populated into the grid. I hardwired the C++ adaptor to 'psi01' rather than the character array name in case their was a problem with the way the string was passed. I had checked that name contained the correct characters, but I figured hardwiring would be safer at this stage. Anything else that you think I should try? Thanks, Lucas From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf of Andy Bauer [andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 12:49 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 I think the problem is that: Clip1 = Clip( guiName=Clip1, InsideOut=0, Scalars=['POINTS', ''], Value=95.0, UseValueAsOffset=0, Crinkleclip=0, ClipType=Scalar ) Should probably have the name of the point data field set in it. Do this with (assuming psi01 is the name of the field you want to clip with respect to: Scalars=['POINTS', 'psi01'] My guess is that the scalar field isn't getting set properly. Try adding in: w = XMLPImageDataWriter(Input=psi01_, FileName = 'fullgrid.pvti') w.UpdatePipeline() right after the CreateProducer() method to see what's in your grid. By the way, does adding in the //char(0) work for converting Fortran strings to C/C++ strings (e.g. in call addfield(psi,psi01//char(0))) ? If it does, will it also work for Fortran77? That's a neat little trick! Andy On Wed, Mar 20, 2013 at 5:29 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.com wrote: I have solved the C++ to Fortran array issues, but I am still not getting a meaningful visualization. I have attached the latest files, including a screenshot of the exported state and the resulting image that is produced by the coprocessor. The coprocessor is generating an error: ERROR: In /Users/lucaspettey/ParaView-git/ParaView/VTK/Filters/General/vtkTableBasedClipDataSet.cxx, line 1956 vtkPVClipDataSet (0x7feaa4998550): no input scalars. This error is not appearing at the time=0 co-process, but it is appearing each time step the co-processor is being asked to write an image. All of the images are the same blank axes as in the attached image0.png. I'm not sure what to try next so any help is appreciated. Thanks, Lucas From: paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org [paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org] on behalf of Pettey . Lucas [lpet...@drc.commailto:lpet...@drc.com] Sent: Wednesday, March 20, 2013 11:45 AM To: Andy Bauer Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 So after some troubleshooting it seems that C++ doesn't like the complex data type the way Fortran is sending it. The code runs when I just send a real value. Images appear, but of course they are meaningless since it isn't the correct data. I may try passing the real and imaginary separate. I may also look into row/column order issues although this grid is 100x100x100 so it shouldn't affect anything. Lucas From: paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org [paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org] on behalf of Pettey . Lucas [lpet...@drc.commailto:lpet...@drc.com] Sent: Wednesday, March 20, 2013 11:12 AM To: Andy Bauer Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Hi Andy and Berk, Here is the error that I am receiving. I know that it is initializing ok and failing at the first call to the co-processor. I have attached my python script output as well as my test code and adaptors. CoProcessingExample(19247,0x7fff77470180) malloc: *** mmap(size=3739605888335872) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug Operating system error: Cannot allocate memory Memory allocation failed Thanks for the help, Lucas From: Andy Bauer [andy.ba...@kitware.commailto:andy.ba...@kitware.com] Sent: Wednesday, March 20, 2013 9:08 AM To: Pettey . Lucas Cc: Berk Geveci; paraview [paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Hi Lucas, Can you share your co-processing script and any run output? There may be warnings in the output or info in the script that will help figure that out. Thanks, Andy On Wed, Mar 20, 2013 at 10:04 AM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com wrote: Hi Berk, Thanks for the help. I found
Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
Yes I did. I have attached the latest script. Thank you for your valiant efforts in trying to solve this problem. Lucas From: Andy Bauer [andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 2:22 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Did you also include the w.UpdatePipeline() part after the writer was created? It won't create the file unless that's in there. Andy On Thu, Mar 21, 2013 at 3:17 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.com wrote: Hi Andy, Changing to Scalars=['POINTS','psi01'] did not change anything. I still get the same error and blank image. I tried adding the XMLPImageDataWriter command, but no file 'fullgrid.pvti' was produced so I can't tell what is being populated into the grid. I hardwired the C++ adaptor to 'psi01' rather than the character array name in case their was a problem with the way the string was passed. I had checked that name contained the correct characters, but I figured hardwiring would be safer at this stage. Anything else that you think I should try? Thanks, Lucas From: paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org [paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org] on behalf of Andy Bauer [andy.ba...@kitware.commailto:andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 12:49 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 I think the problem is that: Clip1 = Clip( guiName=Clip1, InsideOut=0, Scalars=['POINTS', ''], Value=95.0, UseValueAsOffset=0, Crinkleclip=0, ClipType=Scalar ) Should probably have the name of the point data field set in it. Do this with (assuming psi01 is the name of the field you want to clip with respect to: Scalars=['POINTS', 'psi01'] My guess is that the scalar field isn't getting set properly. Try adding in: w = XMLPImageDataWriter(Input=psi01_, FileName = 'fullgrid.pvti') w.UpdatePipeline() right after the CreateProducer() method to see what's in your grid. By the way, does adding in the //char(0) work for converting Fortran strings to C/C++ strings (e.g. in call addfield(psi,psi01//char(0))) ? If it does, will it also work for Fortran77? That's a neat little trick! Andy On Wed, Mar 20, 2013 at 5:29 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com wrote: I have solved the C++ to Fortran array issues, but I am still not getting a meaningful visualization. I have attached the latest files, including a screenshot of the exported state and the resulting image that is produced by the coprocessor. The coprocessor is generating an error: ERROR: In /Users/lucaspettey/ParaView-git/ParaView/VTK/Filters/General/vtkTableBasedClipDataSet.cxx, line 1956 vtkPVClipDataSet (0x7feaa4998550): no input scalars. This error is not appearing at the time=0 co-process, but it is appearing each time step the co-processor is being asked to write an image. All of the images are the same blank axes as in the attached image0.png. I'm not sure what to try next so any help is appreciated. Thanks, Lucas From: paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org [paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org] on behalf of Pettey . Lucas [lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com] Sent: Wednesday, March 20, 2013 11:45 AM To: Andy Bauer Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 So after some troubleshooting it seems that C++ doesn't like the complex data type the way Fortran is sending it. The code runs when I just send a real value. Images appear, but of course they are meaningless since it isn't the correct data. I may try passing the real and imaginary separate. I may also look into row/column order issues although this grid is 100x100x100 so it shouldn't affect anything. Lucas From: paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org [paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org] on behalf of Pettey . Lucas [lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com] Sent: Wednesday, March 20, 2013 11:12 AM To: Andy Bauer Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview
Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
Sorry, Andy, that didn't seem to work either. Let me know what information would be useful to print. Thanks Lucas From: Andy Bauer [andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 2:36 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Hmm, how about trying replacing those two lines with: ParallelImageDataWriter1 = CreateCPWriter( XMLPImageDataWriter, fullgrid_%t.pvti, 1, cp_writers ) Let me know how that goes. If not, I think we'll need to put some print statements in there. Andy On Thu, Mar 21, 2013 at 3:31 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.com wrote: Yes I did. I have attached the latest script. Thank you for your valiant efforts in trying to solve this problem. Lucas From: Andy Bauer [andy.ba...@kitware.commailto:andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 2:22 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Did you also include the w.UpdatePipeline() part after the writer was created? It won't create the file unless that's in there. Andy On Thu, Mar 21, 2013 at 3:17 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com wrote: Hi Andy, Changing to Scalars=['POINTS','psi01'] did not change anything. I still get the same error and blank image. I tried adding the XMLPImageDataWriter command, but no file 'fullgrid.pvti' was produced so I can't tell what is being populated into the grid. I hardwired the C++ adaptor to 'psi01' rather than the character array name in case their was a problem with the way the string was passed. I had checked that name contained the correct characters, but I figured hardwiring would be safer at this stage. Anything else that you think I should try? Thanks, Lucas From: paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org [paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org] on behalf of Andy Bauer [andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 12:49 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 I think the problem is that: Clip1 = Clip( guiName=Clip1, InsideOut=0, Scalars=['POINTS', ''], Value=95.0, UseValueAsOffset=0, Crinkleclip=0, ClipType=Scalar ) Should probably have the name of the point data field set in it. Do this with (assuming psi01 is the name of the field you want to clip with respect to: Scalars=['POINTS', 'psi01'] My guess is that the scalar field isn't getting set properly. Try adding in: w = XMLPImageDataWriter(Input=psi01_, FileName = 'fullgrid.pvti') w.UpdatePipeline() right after the CreateProducer() method to see what's in your grid. By the way, does adding in the //char(0) work for converting Fortran strings to C/C++ strings (e.g. in call addfield(psi,psi01//char(0))) ? If it does, will it also work for Fortran77? That's a neat little trick! Andy On Wed, Mar 20, 2013 at 5:29 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com wrote: I have solved the C++ to Fortran array issues, but I am still not getting a meaningful visualization. I have attached the latest files, including a screenshot of the exported state and the resulting image that is produced by the coprocessor. The coprocessor is generating an error: ERROR: In /Users/lucaspettey/ParaView-git/ParaView/VTK/Filters/General/vtkTableBasedClipDataSet.cxx, line 1956 vtkPVClipDataSet (0x7feaa4998550): no input scalars. This error is not appearing at the time=0 co-process, but it is appearing each time step the co-processor is being asked to write an image. All of the images are the same blank axes as in the attached image0.png. I'm not sure what to try next so any help is appreciated. Thanks, Lucas From: paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org [paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun
Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
Nothing printed at all. Does anything special have to be done during the compile/link steps for the python script to work properly? Thanks, Lucas From: Andy Bauer [andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 3:00 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 How about trying: psi01_.UpdatePipeline() print psi01_.GetDataInformation().DataInformation.GetNumberOfPoints() right about where the writer was created. This will give print out the number of points in the data set that you have. Andy On Thu, Mar 21, 2013 at 3:47 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.com wrote: Sorry, Andy, that didn't seem to work either. Let me know what information would be useful to print. Thanks Lucas From: Andy Bauer [andy.ba...@kitware.commailto:andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 2:36 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Hmm, how about trying replacing those two lines with: ParallelImageDataWriter1 = CreateCPWriter( XMLPImageDataWriter, fullgrid_%t.pvti, 1, cp_writers ) Let me know how that goes. If not, I think we'll need to put some print statements in there. Andy On Thu, Mar 21, 2013 at 3:31 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com wrote: Yes I did. I have attached the latest script. Thank you for your valiant efforts in trying to solve this problem. Lucas From: Andy Bauer [andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 2:22 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Did you also include the w.UpdatePipeline() part after the writer was created? It won't create the file unless that's in there. Andy On Thu, Mar 21, 2013 at 3:17 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com wrote: Hi Andy, Changing to Scalars=['POINTS','psi01'] did not change anything. I still get the same error and blank image. I tried adding the XMLPImageDataWriter command, but no file 'fullgrid.pvti' was produced so I can't tell what is being populated into the grid. I hardwired the C++ adaptor to 'psi01' rather than the character array name in case their was a problem with the way the string was passed. I had checked that name contained the correct characters, but I figured hardwiring would be safer at this stage. Anything else that you think I should try? Thanks, Lucas From: paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org [paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org] on behalf of Andy Bauer [andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 12:49 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 I think the problem is that: Clip1 = Clip( guiName=Clip1, InsideOut=0, Scalars=['POINTS', ''], Value=95.0, UseValueAsOffset=0, Crinkleclip=0, ClipType=Scalar ) Should probably have the name of the point data field set in it. Do this with (assuming psi01 is the name of the field you want to clip with respect to: Scalars=['POINTS', 'psi01'] My guess is that the scalar field isn't getting set properly. Try adding in: w = XMLPImageDataWriter(Input=psi01_, FileName = 'fullgrid.pvti') w.UpdatePipeline() right after the CreateProducer() method to see what's in your grid. By the way, does adding in the //char(0) work for converting Fortran strings to C/C++ strings (e.g. in call addfield(psi,psi01//char(0))) ? If it does, will it also work
Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
Also something weird that I have noted. The Initialize Helper Script line prints twice when I run the Fortran code and no print statements anywhere in my Python script execute (not even if they are at the top). When I run the C++ example located here: http://www.itk.org/Wiki/Coprocessing_example, the Initialize Helper Script only appears once and print statements in the Python script execute normally. I'm not sure if this helps or makes things worse. Thanks, Lucas From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf of Pettey . Lucas [lpet...@drc.com] Sent: Thursday, March 21, 2013 3:12 PM To: Andy Bauer Cc: paraview [paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Nothing printed at all. Does anything special have to be done during the compile/link steps for the python script to work properly? Thanks, Lucas From: Andy Bauer [andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 3:00 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 How about trying: psi01_.UpdatePipeline() print psi01_.GetDataInformation().DataInformation.GetNumberOfPoints() right about where the writer was created. This will give print out the number of points in the data set that you have. Andy On Thu, Mar 21, 2013 at 3:47 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.com wrote: Sorry, Andy, that didn't seem to work either. Let me know what information would be useful to print. Thanks Lucas From: Andy Bauer [andy.ba...@kitware.commailto:andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 2:36 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Hmm, how about trying replacing those two lines with: ParallelImageDataWriter1 = CreateCPWriter( XMLPImageDataWriter, fullgrid_%t.pvti, 1, cp_writers ) Let me know how that goes. If not, I think we'll need to put some print statements in there. Andy On Thu, Mar 21, 2013 at 3:31 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com wrote: Yes I did. I have attached the latest script. Thank you for your valiant efforts in trying to solve this problem. Lucas From: Andy Bauer [andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 2:22 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98 Did you also include the w.UpdatePipeline() part after the writer was created? It won't create the file unless that's in there. Andy On Thu, Mar 21, 2013 at 3:17 PM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com wrote: Hi Andy, Changing to Scalars=['POINTS','psi01'] did not change anything. I still get the same error and blank image. I tried adding the XMLPImageDataWriter command, but no file 'fullgrid.pvti' was produced so I can't tell what is being populated into the grid. I hardwired the C++ adaptor to 'psi01' rather than the character array name in case their was a problem with the way the string was passed. I had checked that name contained the correct characters, but I figured hardwiring would be safer at this stage. Anything else that you think I should try? Thanks, Lucas From: paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org [paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.orgmailto:paraview-boun...@paraview.org] on behalf of Andy Bauer [andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.commailto:andy.ba...@kitware.com] Sent: Thursday, March 21, 2013 12:49 PM To: Pettey . Lucas Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.orgmailto:paraview@paraview.org] Subject: Re: [Paraview
Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
Hi Berk,
Thanks for the help.
I found that this example is written based on an earlier version of VTK so some
of the function calls have changed. Based on your advice and some of the
examples contained in the ParaView wiki, I have gotten it to compile and run.
Now I just have to figure out why it isn't generating any VTK objects
Probably something wrong with my python co-processing script.
Thanks
Lucas
From: Berk Geveci [berk.gev...@kitware.com]
Sent: Tuesday, March 19, 2013 6:48 PM
To: Pettey . Lucas
Cc: paraview [paraview@paraview.org]
Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
You can simply delete this line:
Grid-SetNumberOfScalarComponents(2);
It is redundant given the following later:
field-SetNumberOfComponents(2);
You also need to #include vtkSmartPointer.h.
Best,
-berk
On Tue, Mar 19, 2013 at 2:31 PM, Pettey . Lucas
lpet...@drc.commailto:lpet...@drc.com wrote:
Hello everyone,
I am trying to run a simple Fortran coprocessing example with a complex data
type. I am following the example here:
http://en.wikibooks.org/wiki/Parallel_Spectral_Numerical_Methods/Visualization_with_ParaView_CoProcessing#ParaView_CoProcessing_Resources
I have written a basic Fortran code that outputs the data in binary, opened
that in ParaView, output the coprocessing script and then written the adaptor
following the example in the above link. My adaptor looks like:
extern C void createcpimagedata_(int* nx, int* ny, int* nz)
{
if (!ParaViewCoProcessing::GetCoProcessorData()) {
vtkGenericWarningMacro(Unable to access CoProcessorData.);
return;
}
// The simulation grid is a 2-dimensional topologically and geometrically
// regular grid. In VTK/ParaView, this is considered an image data set.
vtkImageData* Grid = vtkImageData::New();
// assuming dimZ == 1 for now
Grid-SetDimensions(*nx, *ny, *nz);
Grid-SetNumberOfScalarComponents(2);
// Setting the Origin and Spacing are also options.
// Name should be consistent between here, Fortran and Python client script.
ParaViewCoProcessing::GetCoProcessorData()-GetInputDescriptionByName(input)-SetGrid(Grid);
}
// Add field(s) to the data container.
// Separate from above because this will be dynamic, grid is static.
// Might be an issue, VTK probably assumes row major, but
// omeg probably passed column major...
// by hand name mangling for fortran
extern C void addfield_(double* scalars, char* name)
{
vtkCPInputDataDescription *idd =
ParaViewCoProcessing::GetCoProcessorData()-GetInputDescriptionByName(input);
vtkImageData* Image = vtkImageData::SafeDownCast(idd-GetGrid());
if (!Image) {
vtkGenericWarningMacro(No adaptor grid to attach field data to.);
return;
}
// field name must match that in the fortran code.
if (idd-IsFieldNeeded(name)) {
vtkSmartPointervtkDoubleArray field =
vtkSmartPointervtkDoubleArray::New();
field-SetNumberOfComponents(2);
field-SetName(name);
field-SetArray(scalars, 2* Image-GetNumberOfPoints(), 1);
Image-GetPointData()-AddArray(field);
}
}
I am getting some errors from the Makefile generated by Cmake:
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:40:38: error: too few arguments to
function call, expected 2, have 1
Grid-SetNumberOfScalarComponents(2);
~ ^
/Users/lucaspettey/ParaView-git/ParaView/VTK/Common/DataModel/vtkImageData.h:298:3:
note: 'SetNumberOfScalarComponents' declared here
static void SetNumberOfScalarComponents( int n, vtkInformation* meta_data);
^
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:67:5: error: unknown type name
'vtkSmartPointer'; did you mean 'vtkSmartPointerBase'?
vtkSmartPointervtkDoubleArray field =
vtkSmartPointervtkDoubleArray::New();
^~~
vtkSmartPointerBase
/Users/lucaspettey/ParaView-git/ParaView/VTK/Common/Core/vtkOStreamWrapper.h:36:7:
note: 'vtkSmartPointerBase' declared here
class vtkSmartPointerBase;
^
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:67:20: error: expected unqualified-id
vtkSmartPointervtkDoubleArray field =
vtkSmartPointervtkDoubleArray::New();
^
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:68:5: error: use of undeclared
identifier 'field'
field-SetNumberOfComponents(2);
^
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:69:5: error: use of undeclared
identifier 'field'
field-SetName(name);
^
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:70:5: error: use of undeclared
identifier 'field'
field-SetArray(scalars, 2* Image-GetNumberOfPoints(), 1);
^
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:71:37: error: use of undeclared
identifier 'field'
Image-GetPointData()-AddArray(field);
^
Any help is appreciated.
Thanks,
Lucas
This electronic message transmission and any attachments that accompany it
contain information from DRC® (Dynamics Research Corporation) or its
Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
Hi Andy and Berk,
Here is the error that I am receiving.
I know that it is initializing ok and failing at the first call to the
co-processor. I have attached my python script output as well as my test code
and adaptors.
CoProcessingExample(19247,0x7fff77470180) malloc: ***
mmap(size=3739605888335872) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Operating system error: Cannot allocate memory
Memory allocation failed
Thanks for the help,
Lucas
From: Andy Bauer [andy.ba...@kitware.com]
Sent: Wednesday, March 20, 2013 9:08 AM
To: Pettey . Lucas
Cc: Berk Geveci; paraview [paraview@paraview.org]
Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
Hi Lucas,
Can you share your co-processing script and any run output? There may be
warnings in the output or info in the script that will help figure that out.
Thanks,
Andy
On Wed, Mar 20, 2013 at 10:04 AM, Pettey . Lucas
lpet...@drc.commailto:lpet...@drc.com wrote:
Hi Berk,
Thanks for the help.
I found that this example is written based on an earlier version of VTK so some
of the function calls have changed. Based on your advice and some of the
examples contained in the ParaView wiki, I have gotten it to compile and run.
Now I just have to figure out why it isn't generating any VTK objects
Probably something wrong with my python co-processing script.
Thanks
Lucas
From: Berk Geveci [berk.gev...@kitware.commailto:berk.gev...@kitware.com]
Sent: Tuesday, March 19, 2013 6:48 PM
To: Pettey . Lucas
Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.org]
Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
You can simply delete this line:
Grid-SetNumberOfScalarComponents(2);
It is redundant given the following later:
field-SetNumberOfComponents(2);
You also need to #include vtkSmartPointer.h.
Best,
-berk
On Tue, Mar 19, 2013 at 2:31 PM, Pettey . Lucas
lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com
wrote:
Hello everyone,
I am trying to run a simple Fortran coprocessing example with a complex data
type. I am following the example here:
http://en.wikibooks.org/wiki/Parallel_Spectral_Numerical_Methods/Visualization_with_ParaView_CoProcessing#ParaView_CoProcessing_Resources
I have written a basic Fortran code that outputs the data in binary, opened
that in ParaView, output the coprocessing script and then written the adaptor
following the example in the above link. My adaptor looks like:
extern C void createcpimagedata_(int* nx, int* ny, int* nz)
{
if (!ParaViewCoProcessing::GetCoProcessorData()) {
vtkGenericWarningMacro(Unable to access CoProcessorData.);
return;
}
// The simulation grid is a 2-dimensional topologically and geometrically
// regular grid. In VTK/ParaView, this is considered an image data set.
vtkImageData* Grid = vtkImageData::New();
// assuming dimZ == 1 for now
Grid-SetDimensions(*nx, *ny, *nz);
Grid-SetNumberOfScalarComponents(2);
// Setting the Origin and Spacing are also options.
// Name should be consistent between here, Fortran and Python client script.
ParaViewCoProcessing::GetCoProcessorData()-GetInputDescriptionByName(input)-SetGrid(Grid);
}
// Add field(s) to the data container.
// Separate from above because this will be dynamic, grid is static.
// Might be an issue, VTK probably assumes row major, but
// omeg probably passed column major...
// by hand name mangling for fortran
extern C void addfield_(double* scalars, char* name)
{
vtkCPInputDataDescription *idd =
ParaViewCoProcessing::GetCoProcessorData()-GetInputDescriptionByName(input);
vtkImageData* Image = vtkImageData::SafeDownCast(idd-GetGrid());
if (!Image) {
vtkGenericWarningMacro(No adaptor grid to attach field data to.);
return;
}
// field name must match that in the fortran code.
if (idd-IsFieldNeeded(name)) {
vtkSmartPointervtkDoubleArray field =
vtkSmartPointervtkDoubleArray::New();
field-SetNumberOfComponents(2);
field-SetName(name);
field-SetArray(scalars, 2* Image-GetNumberOfPoints(), 1);
Image-GetPointData()-AddArray(field);
}
}
I am getting some errors from the Makefile generated by Cmake:
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:40:38: error: too few arguments to
function call, expected 2, have 1
Grid-SetNumberOfScalarComponents(2);
~ ^
/Users/lucaspettey/ParaView-git/ParaView/VTK/Common/DataModel/vtkImageData.h:298:3:
note: 'SetNumberOfScalarComponents' declared here
static void SetNumberOfScalarComponents( int n, vtkInformation* meta_data);
^
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:67:5: error: unknown type name
'vtkSmartPointer'; did you mean 'vtkSmartPointerBase'?
vtkSmartPointervtkDoubleArray field =
vtkSmartPointervtkDoubleArray::New();
^~~
vtkSmartPointerBase
/Users/lucaspettey/ParaView-git/ParaView/VTK
Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
So after some troubleshooting it seems that C++ doesn't like the complex data
type the way Fortran is sending it.
The code runs when I just send a real value. Images appear, but of course they
are meaningless since it isn't the correct data. I may try passing the real and
imaginary separate. I may also look into row/column order issues although this
grid is 100x100x100 so it shouldn't affect anything.
Lucas
From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf
of Pettey . Lucas [lpet...@drc.com]
Sent: Wednesday, March 20, 2013 11:12 AM
To: Andy Bauer
Cc: paraview [paraview@paraview.org]
Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
Hi Andy and Berk,
Here is the error that I am receiving.
I know that it is initializing ok and failing at the first call to the
co-processor. I have attached my python script output as well as my test code
and adaptors.
CoProcessingExample(19247,0x7fff77470180) malloc: ***
mmap(size=3739605888335872) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Operating system error: Cannot allocate memory
Memory allocation failed
Thanks for the help,
Lucas
From: Andy Bauer [andy.ba...@kitware.com]
Sent: Wednesday, March 20, 2013 9:08 AM
To: Pettey . Lucas
Cc: Berk Geveci; paraview [paraview@paraview.org]
Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
Hi Lucas,
Can you share your co-processing script and any run output? There may be
warnings in the output or info in the script that will help figure that out.
Thanks,
Andy
On Wed, Mar 20, 2013 at 10:04 AM, Pettey . Lucas
lpet...@drc.commailto:lpet...@drc.com wrote:
Hi Berk,
Thanks for the help.
I found that this example is written based on an earlier version of VTK so some
of the function calls have changed. Based on your advice and some of the
examples contained in the ParaView wiki, I have gotten it to compile and run.
Now I just have to figure out why it isn't generating any VTK objects
Probably something wrong with my python co-processing script.
Thanks
Lucas
From: Berk Geveci [berk.gev...@kitware.commailto:berk.gev...@kitware.com]
Sent: Tuesday, March 19, 2013 6:48 PM
To: Pettey . Lucas
Cc: paraview [paraview@paraview.orgmailto:paraview@paraview.org]
Subject: Re: [Paraview] CoProcessing with Fortran and ParaView 3.98
You can simply delete this line:
Grid-SetNumberOfScalarComponents(2);
It is redundant given the following later:
field-SetNumberOfComponents(2);
You also need to #include vtkSmartPointer.h.
Best,
-berk
On Tue, Mar 19, 2013 at 2:31 PM, Pettey . Lucas
lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.commailto:lpet...@drc.com
wrote:
Hello everyone,
I am trying to run a simple Fortran coprocessing example with a complex data
type. I am following the example here:
http://en.wikibooks.org/wiki/Parallel_Spectral_Numerical_Methods/Visualization_with_ParaView_CoProcessing#ParaView_CoProcessing_Resources
I have written a basic Fortran code that outputs the data in binary, opened
that in ParaView, output the coprocessing script and then written the adaptor
following the example in the above link. My adaptor looks like:
extern C void createcpimagedata_(int* nx, int* ny, int* nz)
{
if (!ParaViewCoProcessing::GetCoProcessorData()) {
vtkGenericWarningMacro(Unable to access CoProcessorData.);
return;
}
// The simulation grid is a 2-dimensional topologically and geometrically
// regular grid. In VTK/ParaView, this is considered an image data set.
vtkImageData* Grid = vtkImageData::New();
// assuming dimZ == 1 for now
Grid-SetDimensions(*nx, *ny, *nz);
Grid-SetNumberOfScalarComponents(2);
// Setting the Origin and Spacing are also options.
// Name should be consistent between here, Fortran and Python client script.
ParaViewCoProcessing::GetCoProcessorData()-GetInputDescriptionByName(input)-SetGrid(Grid);
}
// Add field(s) to the data container.
// Separate from above because this will be dynamic, grid is static.
// Might be an issue, VTK probably assumes row major, but
// omeg probably passed column major...
// by hand name mangling for fortran
extern C void addfield_(double* scalars, char* name)
{
vtkCPInputDataDescription *idd =
ParaViewCoProcessing::GetCoProcessorData()-GetInputDescriptionByName(input);
vtkImageData* Image = vtkImageData::SafeDownCast(idd-GetGrid());
if (!Image) {
vtkGenericWarningMacro(No adaptor grid to attach field data to.);
return;
}
// field name must match that in the fortran code.
if (idd-IsFieldNeeded(name)) {
vtkSmartPointervtkDoubleArray field =
vtkSmartPointervtkDoubleArray::New();
field-SetNumberOfComponents(2);
field-SetName(name);
field-SetArray(scalars, 2* Image-GetNumberOfPoints(), 1);
Image-GetPointData()-AddArray(field);
}
}
I am getting some errors from
[Paraview] CoProcessing with Fortran and ParaView 3.98
Hello everyone,
I am trying to run a simple Fortran coprocessing example with a complex data
type. I am following the example here:
http://en.wikibooks.org/wiki/Parallel_Spectral_Numerical_Methods/Visualization_with_ParaView_CoProcessing#ParaView_CoProcessing_Resources
I have written a basic Fortran code that outputs the data in binary, opened
that in ParaView, output the coprocessing script and then written the adaptor
following the example in the above link. My adaptor looks like:
extern C void createcpimagedata_(int* nx, int* ny, int* nz)
{
if (!ParaViewCoProcessing::GetCoProcessorData()) {
vtkGenericWarningMacro(Unable to access CoProcessorData.);
return;
}
// The simulation grid is a 2-dimensional topologically and geometrically
// regular grid. In VTK/ParaView, this is considered an image data set.
vtkImageData* Grid = vtkImageData::New();
// assuming dimZ == 1 for now
Grid-SetDimensions(*nx, *ny, *nz);
Grid-SetNumberOfScalarComponents(2);
// Setting the Origin and Spacing are also options.
// Name should be consistent between here, Fortran and Python client script.
ParaViewCoProcessing::GetCoProcessorData()-GetInputDescriptionByName(input)-SetGrid(Grid);
}
// Add field(s) to the data container.
// Separate from above because this will be dynamic, grid is static.
// Might be an issue, VTK probably assumes row major, but
// omeg probably passed column major...
// by hand name mangling for fortran
extern C void addfield_(double* scalars, char* name)
{
vtkCPInputDataDescription *idd =
ParaViewCoProcessing::GetCoProcessorData()-GetInputDescriptionByName(input);
vtkImageData* Image = vtkImageData::SafeDownCast(idd-GetGrid());
if (!Image) {
vtkGenericWarningMacro(No adaptor grid to attach field data to.);
return;
}
// field name must match that in the fortran code.
if (idd-IsFieldNeeded(name)) {
vtkSmartPointervtkDoubleArray field =
vtkSmartPointervtkDoubleArray::New();
field-SetNumberOfComponents(2);
field-SetName(name);
field-SetArray(scalars, 2* Image-GetNumberOfPoints(), 1);
Image-GetPointData()-AddArray(field);
}
}
I am getting some errors from the Makefile generated by Cmake:
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:40:38: error: too few arguments to
function call, expected 2, have 1
Grid-SetNumberOfScalarComponents(2);
~ ^
/Users/lucaspettey/ParaView-git/ParaView/VTK/Common/DataModel/vtkImageData.h:298:3:
note: 'SetNumberOfScalarComponents' declared here
static void SetNumberOfScalarComponents( int n, vtkInformation* meta_data);
^
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:67:5: error: unknown type name
'vtkSmartPointer'; did you mean 'vtkSmartPointerBase'?
vtkSmartPointervtkDoubleArray field =
vtkSmartPointervtkDoubleArray::New();
^~~
vtkSmartPointerBase
/Users/lucaspettey/ParaView-git/ParaView/VTK/Common/Core/vtkOStreamWrapper.h:36:7:
note: 'vtkSmartPointerBase' declared here
class vtkSmartPointerBase;
^
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:67:20: error: expected unqualified-id
vtkSmartPointervtkDoubleArray field =
vtkSmartPointervtkDoubleArray::New();
^
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:68:5: error: use of undeclared
identifier 'field'
field-SetNumberOfComponents(2);
^
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:69:5: error: use of undeclared
identifier 'field'
field-SetName(name);
^
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:70:5: error: use of undeclared
identifier 'field'
field-SetArray(scalars, 2* Image-GetNumberOfPoints(), 1);
^
/Users/lucaspettey/codes/BEC/coprocVTK.cxx:71:37: error: use of undeclared
identifier 'field'
Image-GetPointData()-AddArray(field);
^
Any help is appreciated.
Thanks,
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
Visit other Kitware open-source projects at
Re: [Paraview] ENABLE_MPI4PY on Mac OSX
Hi Nikhi, I was able to compile ParaView with the ENABLE_MPI4PY using the 3.98.1 in the git repository. For future record, I had to download Python 2.7.3 rather than the Apple supplied 2.7.2. I also installed NumPy, SciPy, MatPlotLib and MPI4PY from their sources. I'm not sure which of these solved the problem, but it works with these steps. Thanks, Lucas From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf of Pettey . Lucas [lpet...@drc.com] Sent: Thursday, February 07, 2013 1:49 PM To: Nikhil Shetty Cc: paraview@paraview.org Subject: Re: [Paraview] ENABLE_MPI4PY on Mac OSX Hi Nikhi, My system details: Mac Pro Mid 2012 OSX 10.8.2 Python: Python 2.7.2 (default, Jun 20 2012, 16:23:33) [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin Type help, copyright, credits or license for more information. dlopen(/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/readline.so, 2); import readline # dynamically loaded from /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/readline.so MPI is OpenMPI 1.6.3 built from source MPI4PY is 1.3 also built from source Here is the error message: [100%] Generating mpi4py/pv_mpi_compile_complete Listing /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py ... Compiling /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py/MPI.py ... Compiling /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py/__init__.py ... Compiling /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py/compile_all_pv_mpi.py ... Listing /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py/include ... Listing /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py/include/mpi4py ... Compiling /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py/rc.py ... [100%] Built target paraview_mpi_pyc Scanning dependencies of target MPIPython [100%] Building C object Utilities/mpi4py/Library/CMakeFiles/MPIPython.dir/MPI.c.o Linking CXX shared module ../../../lib/MPIPython.so Undefined symbols for architecture x86_64: _lt_dladvise_destroy, referenced from: _dlopen_mpi_lib in MPI.c.o _lt_dladvise_ext, referenced from: _dlopen_mpi_lib in MPI.c.o _lt_dladvise_global, referenced from: _dlopen_mpi_lib in MPI.c.o _lt_dladvise_init, referenced from: _dlopen_mpi_lib in MPI.c.o _lt_dlclose, referenced from: _dlclose_mpi_lib in MPI.c.o _lt_dlexit, referenced from: _dlclose_mpi_lib in MPI.c.o _lt_dlinit, referenced from: _dlopen_mpi_lib in MPI.c.o _lt_dlopenadvise, referenced from: _dlopen_mpi_lib in MPI.c.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: *** [lib/MPIPython.so] Error 1 make[1]: *** [Utilities/mpi4py/Library/CMakeFiles/MPIPython.dir/all] Error 2 make: *** [all] Error 2 Any help is appreciated. Thanks Lucas From: Nikhil Shetty [nikhil.she...@kitware.com] Sent: Thursday, February 07, 2013 10:45 AM To: Pettey . Lucas Cc: paraview@paraview.org Subject: Re: [Paraview] ENABLE_MPI4PY on Mac OSX Hi Lucas, Can you tell what MAC, Python and MPI versions you are using. Also can you attach the complete message about which symbols are not being found. -Nikhi On Thu, Feb 7, 2013 at 11:32 AM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.com wrote: Hello, Has anyone had success with enabling MPI4PY on the Mac? I rebuilt the latest version of mpi4py from source and it still doesn't build in ParaView. I get the undefined symbols for architecture x86_64 errors. Thanks 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.comhttp://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] ENABLE_MPI4PY on Mac OSX
Hello, Has anyone had success with enabling MPI4PY on the Mac? I rebuilt the latest version of mpi4py from source and it still doesn't build in ParaView. I get the undefined symbols for architecture x86_64 errors. Thanks 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 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
Re: [Paraview] ENABLE_MPI4PY on Mac OSX
Hi Nikhi, My system details: Mac Pro Mid 2012 OSX 10.8.2 Python: Python 2.7.2 (default, Jun 20 2012, 16:23:33) [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin Type help, copyright, credits or license for more information. dlopen(/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/readline.so, 2); import readline # dynamically loaded from /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/readline.so MPI is OpenMPI 1.6.3 built from source MPI4PY is 1.3 also built from source Here is the error message: [100%] Generating mpi4py/pv_mpi_compile_complete Listing /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py ... Compiling /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py/MPI.py ... Compiling /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py/__init__.py ... Compiling /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py/compile_all_pv_mpi.py ... Listing /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py/include ... Listing /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py/include/mpi4py ... Compiling /Users/lucaspettey/ParaView-3.98/Utilities/mpi4py/mpi4py/rc.py ... [100%] Built target paraview_mpi_pyc Scanning dependencies of target MPIPython [100%] Building C object Utilities/mpi4py/Library/CMakeFiles/MPIPython.dir/MPI.c.o Linking CXX shared module ../../../lib/MPIPython.so Undefined symbols for architecture x86_64: _lt_dladvise_destroy, referenced from: _dlopen_mpi_lib in MPI.c.o _lt_dladvise_ext, referenced from: _dlopen_mpi_lib in MPI.c.o _lt_dladvise_global, referenced from: _dlopen_mpi_lib in MPI.c.o _lt_dladvise_init, referenced from: _dlopen_mpi_lib in MPI.c.o _lt_dlclose, referenced from: _dlclose_mpi_lib in MPI.c.o _lt_dlexit, referenced from: _dlclose_mpi_lib in MPI.c.o _lt_dlinit, referenced from: _dlopen_mpi_lib in MPI.c.o _lt_dlopenadvise, referenced from: _dlopen_mpi_lib in MPI.c.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: *** [lib/MPIPython.so] Error 1 make[1]: *** [Utilities/mpi4py/Library/CMakeFiles/MPIPython.dir/all] Error 2 make: *** [all] Error 2 Any help is appreciated. Thanks Lucas From: Nikhil Shetty [nikhil.she...@kitware.com] Sent: Thursday, February 07, 2013 10:45 AM To: Pettey . Lucas Cc: paraview@paraview.org Subject: Re: [Paraview] ENABLE_MPI4PY on Mac OSX Hi Lucas, Can you tell what MAC, Python and MPI versions you are using. Also can you attach the complete message about which symbols are not being found. -Nikhi On Thu, Feb 7, 2013 at 11:32 AM, Pettey . Lucas lpet...@drc.commailto:lpet...@drc.com wrote: Hello, Has anyone had success with enabling MPI4PY on the Mac? I rebuilt the latest version of mpi4py from source and it still doesn't build in ParaView. I get the undefined symbols for architecture x86_64 errors. Thanks 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.comhttp://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
Re: [Paraview] XDMF Utilities
Hello, The exact flag is XDMF_BUILD_UTILS. The default is off. Thanks, Lucas From: Utkarsh Ayachit [utkarsh.ayac...@kitware.com] Sent: Tuesday, February 05, 2013 6:16 PM To: Pettey . Lucas Cc: paraview@paraview.org Subject: Re: [Paraview] XDMF Utilities What's the exact name of the Cmake flag? I can do a grep to see what it does. On Tue, Feb 5, 2013 at 5:00 PM, Pettey . Lucas lpet...@drc.com wrote: Hello everyone, I have had quite a bit of difficulty building 3.14.1 on my Mac with XDMF Utilities turned on. I will be reading files in XDMF format. Am I missing anything important if I don't build the utilities? There doesn't seem to be much documentation about what that CMake flag enables. Thanks 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 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
[Paraview] ParaView 3.14.1 ADIOS reader build errors
Hello everyone, I am trying to build ParaView 3.14 with the ADIOS Reader. I have the latest ADIOS 1.4.1 library built. I am receiving the following errors: [ 98%] Building CXX object Plugins/AdiosReader/CMakeFiles/AdiosReaderPluginMPI.dir/vtkAdiosReader.cxx.o In file included from /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosReader.cxx:15: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosReader.h:22: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataSetAlgorithm.h:25: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Filtering/vtkAlgorithm.h:32: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Common/vtkObject.h:41: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Common/vtkObjectBase.h:43: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Common/vtkIndent.h:24: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Common/vtkSystemIncludes.h:40: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Common/vtkIOStream.h:108: In file included from /usr/include/c++/4.2.1/backward/strstream:51: /usr/include/c++/4.2.1/backward/backward_warning.h:32:2: warning: This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the X header for the X.h header for C++ includes, or iostream instead of the deprecated header iostream.h. To disable this warning use -Wno-deprecated. [-W#warnings] #warning This file includes at least one deprecated or antiquated header. \ ^ In file included from /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosReader.cxx:16: /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:108:41: error: no member named 'timedim' in 'ADIOS_VARINFO' this-TimeIndexComponent = varInfo-timedim; // -1 if no time steps ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:110:50: error: no member named 'timedim' in 'ADIOS_VARINFO' this-Dimension = varInfo-ndim - ((varInfo-timedim == -1) ? 0 : 1); // The dimension here do not take the time into account ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:117:18: error: no member named 'gmin' in 'ADIOS_VARINFO' if (varInfo-gmin varInfo-gmax) ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:117:35: error: no member named 'gmax' in 'ADIOS_VARINFO' if (varInfo-gmin varInfo-gmax) ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:121:52: error: no member named 'gmin' in 'ADIOS_VARINFO' this-Range[0] = (double)(*((int*)varInfo-gmin)); ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:122:52: error: no member named 'gmax' in 'ADIOS_VARINFO' this-Range[1] = (double)(*((int*)varInfo-gmax)); ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:126:54: error: no member named 'gmin' in 'ADIOS_VARINFO' this-Range[0] = (double)(*((float*)varInfo-gmin)); ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:127:54: error: no member named 'gmax' in 'ADIOS_VARINFO' this-Range[1] = (double)(*((float*)varInfo-gmax)); ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:131:55: error: no member named 'gmin' in 'ADIOS_VARINFO' this-Range[0] = (double)(*((double*)varInfo-gmin)); ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:132:55: error: no member named 'gmax' in 'ADIOS_VARINFO' this-Range[1] = (double)(*((double*)varInfo-gmax)); ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:139:40: error: no member named 'timedim' in 'ADIOS_VARINFO' if(this-Dimension 3 || varInfo-timedim 0) ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:1468:3: error: unknown type name 'ADIOS_GROUP' ADIOS_GROUP **Groups; ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:397:18: error: use of undeclared identifier 'adios_fopen' this-File = adios_fopen(this-FileName.c_str(), (comm) ? *comm : 0); ^
Re: [Paraview] ParaView 3.14.1 ADIOS reader build errors
Hello again everyone, I talked with the ADIOS developers and they suggested adding to CPPFLAGS the flag -DADIOS_USE_READ_API_1. ParaView 3.14.1 is trying to use the pre-1.4 ADIOS read library and the flag tells ADIOS to revert to the old read system. Hope this helps anyone with a similar issue. Lucas From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on behalf of Pettey . Lucas [lpet...@drc.com] Sent: Wednesday, February 06, 2013 11:25 AM To: paraview@paraview.org Subject: [Paraview] ParaView 3.14.1 ADIOS reader build errors Hello everyone, I am trying to build ParaView 3.14 with the ADIOS Reader. I have the latest ADIOS 1.4.1 library built. I am receiving the following errors: [ 98%] Building CXX object Plugins/AdiosReader/CMakeFiles/AdiosReaderPluginMPI.dir/vtkAdiosReader.cxx.o In file included from /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosReader.cxx:15: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosReader.h:22: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataSetAlgorithm.h:25: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Filtering/vtkAlgorithm.h:32: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Common/vtkObject.h:41: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Common/vtkObjectBase.h:43: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Common/vtkIndent.h:24: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Common/vtkSystemIncludes.h:40: In file included from /Users/lucaspettey/ParaView-3.14.1-Source/VTK/Common/vtkIOStream.h:108: In file included from /usr/include/c++/4.2.1/backward/strstream:51: /usr/include/c++/4.2.1/backward/backward_warning.h:32:2: warning: This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the X header for the X.h header for C++ includes, or iostream instead of the deprecated header iostream.h. To disable this warning use -Wno-deprecated. [-W#warnings] #warning This file includes at least one deprecated or antiquated header. \ ^ In file included from /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosReader.cxx:16: /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:108:41: error: no member named 'timedim' in 'ADIOS_VARINFO' this-TimeIndexComponent = varInfo-timedim; // -1 if no time steps ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:110:50: error: no member named 'timedim' in 'ADIOS_VARINFO' this-Dimension = varInfo-ndim - ((varInfo-timedim == -1) ? 0 : 1); // The dimension here do not take the time into account ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:117:18: error: no member named 'gmin' in 'ADIOS_VARINFO' if (varInfo-gmin varInfo-gmax) ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:117:35: error: no member named 'gmax' in 'ADIOS_VARINFO' if (varInfo-gmin varInfo-gmax) ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:121:52: error: no member named 'gmin' in 'ADIOS_VARINFO' this-Range[0] = (double)(*((int*)varInfo-gmin)); ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:122:52: error: no member named 'gmax' in 'ADIOS_VARINFO' this-Range[1] = (double)(*((int*)varInfo-gmax)); ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:126:54: error: no member named 'gmin' in 'ADIOS_VARINFO' this-Range[0] = (double)(*((float*)varInfo-gmin)); ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:127:54: error: no member named 'gmax' in 'ADIOS_VARINFO' this-Range[1] = (double)(*((float*)varInfo-gmax)); ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:131:55: error: no member named 'gmin' in 'ADIOS_VARINFO' this-Range[0] = (double)(*((double*)varInfo-gmin)); ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source/Plugins/AdiosReader/vtkAdiosInternals.h:132:55: error: no member named 'gmax' in 'ADIOS_VARINFO' this-Range[1] = (double)(*((double*)varInfo-gmax)); ~~~ ^ /Users/lucaspettey/ParaView-3.14.1-Source
[Paraview] XDMF Utilities
Hello everyone, I have had quite a bit of difficulty building 3.14.1 on my Mac with XDMF Utilities turned on. I will be reading files in XDMF format. Am I missing anything important if I don't build the utilities? There doesn't seem to be much documentation about what that CMake flag enables. Thanks 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 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
