[CIG-SHORT] how to turn off vtk output
Brad Aagaard
baagaard at usgs.gov
Wed Nov 22 08:34:07 PST 2017
Tu,
As I mentioned yesterday, you need to set the vertex_data_fields and
cell_data_fields to empty arrays to turn off output. As you can see in
the info you posted, this VTK output is coming from the material.
Here are the steps to follow to figure out how to turn the VTK output off:
1. Load the pylith_parameters.json into the PyLith Parameter Viewer
(follow the instructions in the manual to run it locally or use the
online version at https://geodynamics.github.io/pylith_parameters/).
2. Search for VTK.
For each occurrence, look at the object one level above the data_writer
to see what fields it is writing.
For example: The first occurrence is in
[pylithapp.mesh_generator.distributor.data_writer]. Clicking on
<pylith.topology.Distributor.Distributor> to the right of distributor, I
see under "Details for Selected Component" that writer_partition is
False, so no output will be written for this data writer.
Next, I see a DatWriterVTK for
[pylithapp.problem.materials.crust.output.writer]. Clicking on
<pylith.meshio.OutputMatElastic>, I see the cell_data_fields and
cell_info_fields are not empty arrays.
Looking at the Details for Selected Component, the full path for the
component is
[pylithapp.problem.materials.crust.output]. Notice that all of the
properties and facilities have default values.
So to turn off output, within one of your .cfg files add:
[pylithapp.problem.materials.crust.output]
cell_data_fields = []
cell_info_fields = []
REPEAT for your man material.
Regards,
Brad
On 11/21/2017 04:40 PM, tu xiang wrote:
> Dear Charles
> Yes, the pylith.meshio.DataWriterVTK.DataWriterVTK is set. But I still
> cannot turn off vtk output after I tried many times.
>
> "class": "<pylith.meshio.OutputMatElastic.OutputMatElastic; proxy of
> <Swig Object of type 'pylith::meshio::OutputManager *' at
> 0x7f7fcac68300> >",
> "name": "outputmatelastic",
> "components": {
> "writer": {
> "description": "Writer
> for data.",
> "setFrom": "{default}",
> "class":
> "<pylith.meshio.DataWriterVTK.DataWriterVTK; proxy of <Swig Object of
> type 'pylith::meshio::DataWriterVTK *' at 0x7f7fcac68390> >",
> "name": "datawritervtk",
>
> I attached the pylith_parameters.json file. Yes, the fault output is
> written to an HDF5 file
>
> I also attached the cfg files.
>
> Hope you would help me.
> Best regards
> Tu Xiang
>
>
>
More information about the CIG-SHORT
mailing list