If the user did that, then he/she explicitly set the file extension to be
.pvtm instead of the default .vtm when creating the Catalyst multiblock
dataset writer for the Catalyst script. There is only one XML multiblock
data reader and writer.

When a user adds a writer when making a Catalyst Python script by default
it will have the proper file extension but they are allowed to change that
file extension. The file extension that the user gives the filename doesn't
affect the file format itself (i.e. what writer is used).

Does that make sense?

On Tue, May 15, 2018 at 4:12 PM Scott, W Alan <wasc...@sandia.gov> wrote:

> Again, does this then mean we should delete pvtm file formats Catalyst
> writers?  I have a user that created a pvtm file recently, I believe using
> Catalyst…
>
>
>
> *From: *Andy Bauer <andy.ba...@kitware.com>
> *Date: *Tuesday, May 15, 2018 at 1:00 PM
> *To: *W Scott <wasc...@sandia.gov>
> *Cc: *Utkarsh Ayachit <utkarsh.ayac...@kitware.com>, "
> parav...@paraview.org" <parav...@paraview.org>
> *Subject: *Re: [Paraview] [EXTERNAL] Re: pvtm file format
>
>
>
>
>
> From my investigation and not being able to find any pvtm in either
> today's ParaView or several of the 3.* versions (what Ken's old bug report
> referred to) I'd say that .pvtm was never officially or even unofficially a
> VTK file format extension used by the XML multiblock reader or writer. I'd
> say that .vtm is the one and only XML multiblock data extension and close
> the issue.
>
>
>
> On Tue, May 15, 2018 at 11:48 AM Scott, W Alan <wasc...@sandia.gov> wrote:
>
> Trying to wrap my head around what you said.  Really basic question – is
> .pvtm files a viable file format?  Either it should be supported in
> ParaView readers, or it should be removed from Catalyst and VTK – correct?
>
>
>
> I wrote up a bug here:
> https://gitlab.kitware.com/paraview/paraview/issues/18172
>
>
>
> Alan
>
>
>
> *From: *Andy Bauer <andy.ba...@kitware.com>
> *Date: *Tuesday, May 15, 2018 at 8:33 AM
> *To: *W Scott <wasc...@sandia.gov>
> *Cc: *Utkarsh Ayachit <utkarsh.ayac...@kitware.com>, "
> parav...@paraview.org" <parav...@paraview.org>
> *Subject: *Re: [Paraview] [EXTERNAL] Re: pvtm file format
>
>
>
> Hi Alan,
>
>
>
> I wouldn't describe it as a redundant file format, just a redundant file
> extension (like ExodusII with .e, .ex2, etc.). Actually, looking through
> the PV and VTK source code, like Utkarsh did before, there doesn't look to
> be anything that refers to .pvtm so maybe I'm just remembering things wrong
> here. Looking back though (https://www.vtk.org/Bug/view.php?id=10498) it
> does seem like at one time we used the .pvtm file extension but maybe that
> was by accident though.
>
>
>
> As for writing out files from Catalyst, or even from ParaView, a user can
> select the writer and specify whatever they want for the file extension.
> Maybe that's where the issue arose.
>
>
>
> Best,
>
> Andy
>
>
>
> On Mon, May 14, 2018 at 9:37 PM Scott, W Alan <wasc...@sandia.gov> wrote:
>
> Thanks Andy.  I’m hearing of numerous issues like thus, trying to wrap my
> head around same.
>
>
>
> Let’s start with a few questions.  Where is the .pvtm file format
> documented?  Google doesn’t know...  Next, why have two redundant file
> formats?  One should be deprecated.  Why can Catalyst write this file
> format?  And last, of course, why can’t ParaView read it?
>
>
>
> Alan
>
>
>
> *From:* Andy Bauer [mailto:andy.ba...@kitware.com]
> *Sent:* Monday, May 14, 2018 7:31 PM
> *To:* Scott, W Alan <wasc...@sandia.gov>
> *Cc:* Ayachit, Utkarsh (External Contacts) <utkarsh.ayac...@kitware.com>;
> Paraview (parav...@paraview.org) <parav...@paraview.org>
> *Subject:* Re: [Paraview] [EXTERNAL] Re: pvtm file format
>
>
>
> The .pvtm is the same as the .vtm file, just a redundant file extension.
> Really, the .vtm format is parallel/partition aware where as the other .vt*
> extensions have a partitioned .pvt* format.
>
> I'm a bit surprised that PV doesn't associate the .pvtm file with
> multiblock datasets. If you try to read in a .pvtm file though you just
> need to properly associate it with the XML multiblock data reader.
>
>
>
> On Mon, May 14, 2018 at 9:14 PM Scott, W Alan via ParaView <
> paraview@public.kitware.com> wrote:
>
> I’ve never heard of these files either.  From my user:
>
>
>
>
>
> I am writing planes of data in parallel with XMLMultiBlockWriter and it is
> generating *pvtm files.  However, paraview doesn’t seem to support this
> file format for reading?  I am trying to visualize the results and I can
> read the individual *vtp files, but it doesn’t accept the parallel file.
>
>
>
> Then:
>
>
>
> I will try to put something together for you soon.  I am writing this
> dataset from a slice while running catalyst.  I found a work around by
> using the MergeBlocks filter on the slice and then dumping that as an
> unstructured grid via XMLPUnstructuredGridWriter.
>
>
>
> Back to me.
>
>
>
> “.  I am writing this dataset from a slice while running catalyst.”  So, I
> figured I would start by asking if this is a Catalyst/ ParaView/ VTK file
> format (that I had never heard of)...    I have asked user for a dataset.
>
>
>
> Thanks,
>
>
>
> Alan
>
>
>
>
>
> *From:* Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> *Sent:* Monday, May 14, 2018 7:08 PM
> *To:* Scott, W Alan <wasc...@sandia.gov>
> *Cc:* ParaView <parav...@paraview.org>
> *Subject:* [EXTERNAL] Re: [Paraview] pvtm file format
>
>
>
> I am not sure. A quick grep through the code in ParaView/VTK doesn't yield
> a hit. What's the context in which you encountered this?
>
>
>
> Utkarsh
>
>
>
> On Mon, May 14, 2018 at 9:05 PM Scott, W Alan via ParaView <
> paraview@public.kitware.com> wrote:
>
> What is a .pvtm file?  How can I make one with sources?
>
>
>
> Thanks,
>
>
>
> Alan
>
>
>
> --------------------------------------------------------
>
> W. Alan Scott
>
> ParaView Support Manager
>
>
>
> SAIC
>
> Sandia National Laboratories, MS 0807
>
> Org 9326 - Building 880 A1-K
>
> (505) 284-0932   FAX (505) 284-5619
>
>
>
> “When the facts change, I change my mind. What do you do, sir?”
>
> John Maynard Keynes
>
>
>
> ---------------------------------------------------------
>
>
>
> _______________________________________________
> 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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://public.kitware.com/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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://public.kitware.com/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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview

Reply via email to