Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

In-Situ visualization #475

Closed
aancel opened this issue Nov 14, 2014 · 6 comments
Closed

In-Situ visualization #475

aancel opened this issue Nov 14, 2014 · 6 comments
Assignees
@aancel
Labels
✨ type:feature

Comments

@aancel
Copy link
Contributor

aancel commented Nov 14, 2014

Implement In-situ visualization using Paraview/catalyst and the VTK format (see Issue #474)
@aancel aancel self-assigned this Nov 14, 2014
aancel added a commit that referenced this issue Nov 19, 2014
@aancel
Issue #475:
b94ac1b 
- Added cmake search for ParaView catalyst specific headers/libs
aancel added a commit that referenced this issue Nov 19, 2014
@aancel
Issue #474
90250e5 
- Cleaned up save function code

Issue #475
- Added headers for coprocessing
aancel added a commit that referenced this issue Nov 20, 2014
@aancel
Issue #474 & #475
262efa0 
- Made cmake warnings more explicit
- Show which paraview use file will be used

- Display a message when boost python was not found
aancel added a commit that referenced this issue Nov 21, 2014
@aancel
Issue #475:
621e67b 
- added options for enabling insitu visualization and specifying a custom python
  script for Paraview
- added base code for insitu visualization in exporter (experimental)
aancel added a commit that referenced this issue Nov 27, 2014
@aancel
Issue #474:
93d67d5 
- Refactored code & select vtkMultiBlockDataSet by default
- Select the first field data as default for per node/element data

Issue #475:
- Improved Catalyst code
- Added base script for building catalyst pipeline in ParaView

Other:
- removed tools/ from .gitignore
aancel added a commit that referenced this issue Dec 2, 2014
@aancel
Issue #474 & #475
767a94f 
- Fixed bug in VTK exporter introduced by In-situ changes
aancel added a commit that referenced this issue Dec 3, 2014
@aancel
Issue #474:
ae93982 
- Fixed bad export of pvd meta-files. Data grouping through this files
  now works; File is correctly removed at each simlation restart;
- Fixed bad meta-file generation when using XML Multi block parallel writer (writing exclusion must be done manually);
- Fixed meta-file non parallel version.

Issue #475:
- Fixed transmission of time steps to Paraview through Catalyst.

Other:
- Added a define in timeset.hpp to remember the index of the first time
  step.
@aancel aancel closed this as completed in 88608da Dec 5, 2014
aancel added a commit that referenced this issue Dec 11, 2014
@aancel
Issue #475:
7bc3003 
- Improved compatibilty with the use of a separate pvserver (e.g. on clusters)
- Added options to tell where the pvserver will be located
aancel added a commit that referenced this issue Mar 19, 2015
@aancel
Issue #475:
afe6293 
- C++ implementation (now the default one, when no python scripts are
  specified)
@vincentchabannes
Copy link
Member

@aancel Is it possible to use insitu visualisation with multi exporter. In my fsi code, I have two exporter, one for the fluid, another one for structure. And when I run insitu visu in this case, I have this error :

vtkPVTrivialProducer (0x7fcensions/Core/vtkPVTrivialProducer.cxx, linr.cxx, line 68
vtkPVTrivia39a15a450): New time step isaViewCore/VTKExtensions/Core/vtkPVTrivialProducer.cxx, line 68
vtkPVTrivialProducer (0x7f94b8bdce 68
vtkPVTrivialProducerlProducer (0x7feec87aa97cd0): New time step is not afte0): New time not after last tir last time step.

 (0x7f9d382cabf0): New tim step is not after last time step.
me step.

e step is not after last 
time step.

@aancel
Copy link
Contributor Author

aancel commented Mar 19, 2015

Indeed, I haven't tested this configuration yet.
I think that I have an idea about what is causing you this problem. It tries to use the same proxy object for all the exporter instances, so when you export 2 different datasets for a single time step, it expects a different time step for each, but the same one is used, thus your error.
I hope my explication is clear, but anyway I'll try to push a fix tomorrow and see if it helps with your case.

@vincentchabannes
Copy link
Member

Ok, thank's.

@aancel
Copy link
Contributor Author

aancel commented Mar 20, 2015

@vincentchabannes Ok I had a look and what I thought would be the problem is not the problem in fact.
Do you have a sample code that reproduces this error and that I could use to debug ?
Are you instantiating two separate exporters ?

@vincentchabannes
Copy link
Member

Yes, I have 2 exporters, one 2d and another one 1d (with a RealDim 2d). I am at the airport of Paris and quite tired, thus not operational to give you an example now. We will see that at FUD. Maybe I do a mistake and also I haven't updated your last changes.

aancel added a commit that referenced this issue Mar 27, 2015
@aancel
VTK & In-situ:
6f3990d 
mesh.hpp:
- Use class member to get number of points per element

Issue #474:
- Fixed 3D case mesh
- Improve memory handling

Issue #475:
- Updated base C++ code for In-situ to correctly set output
- Added --exporter.vtk.insitu.save to export data to disk when doing
  in-situ visualization
- Added file extension in CMakeLists
@aancel
Copy link
Contributor Author

aancel commented Mar 27, 2015

@vincentchabannes I added the option --exporter.vtk.insitu.save to save data to disk when doing in-situ visualization.

aancel added a commit that referenced this issue Apr 7, 2015
@aancel
Issue #475:
2bb3d25 
- Fix: correctly updating the block names in in multi block datasets
- Fix: Switch to vtkSMSourceProxy to correclyt update time data on
  ParaView side
aancel added a commit that referenced this issue May 29, 2015
@aancel
Issue #475:
d8e55c5 
- C++ implementation (now the default one, when no python scripts are
  specified)
aancel added a commit that referenced this issue May 29, 2015
@aancel
VTK & In-situ:
bc793ee 
mesh.hpp:
- Use class member to get number of points per element

Issue #474:
- Fixed 3D case mesh
- Improve memory handling

Issue #475:
- Updated base C++ code for In-situ to correctly set output
- Added --exporter.vtk.insitu.save to export data to disk when doing
  in-situ visualization
- Added file extension in CMakeLists
aancel added a commit that referenced this issue May 29, 2015
@aancel
Issue #475:
3f28405 
- Fix: correctly updating the block names in in multi block datasets
- Fix: Switch to vtkSMSourceProxy to correclyt update time data on
  ParaView side
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aancel aancel

Labels
✨ type:feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@prudhomm @vincentchabannes @aancel