[Paraview-developers] How to name blocks in multi-block data set?

[Paul Edwards]

It's possible to store all those things in field data but you would need to
write your own views or representations to use the information as the gui
doesn't currently support it.  Another option might be to put the
information as field data and then have python scripts/macros to set up a
view as you want it (writing views/representations isn't a simple task!)

Regards,
Paul

On 28 June 2013 19:16, Joshua Murphy <Joshua.Murphy at lasp.colorado.edu>wrote:

> Hi Paul,
>
> Great!  That work perfectly!
>
> I have two more questions that maybe you (or someone else) can help me
> with!
>
>
> First, I would like to give each variable a meaningful legend name, so,
> when they are plotted, I can show something better than "OMNI2_HO_MRG1HR…."
> is there a similar meta-data command for changing a variables Legend name?
>  I suppose  a place to store the units would be too much to ask?  I would
> ideally love to store the following information:
>
>
>    1. Legend Name
>    2. Units
>    3. Coordinate System
>
>
> If I could do that, I would be a very happy programmer.
>
> The other thing I need to do is set the default selection to unselected
> when plotting.  This must be possible, as ParaView created variables
> default to unselelected.
>
> The reason for this need is two fold.
>
>
>    1. when looking at space craft data, you rarely want to plot
>    everything all at once, since everything is on vastly different scales
>    2. If you default to all variables, Paravaiew will hang if you have a
>    great many of them to plot.  For an example, if I have 100 variables with
>    10,000 time steps, paraview turns to molasses just trying to UNSELECT
>    everything that is selected.
>
>
> Any help would be great!
>
> Thanks again,
>
> Josh
>
> Joshua J. Murphy
> Computer Scientist
> Laboratory for Atmospheric and Space Physics
> University of Colorado, Boulder
>
> From: Paul Edwards <paul.m.edwards at gmail.com>
> Date: Tuesday, June 25, 2013 10:57 PM
> To: Joshua Murphy <Joshua.Murphy at lasp.colorado.edu>
> Cc: "paraview-developers at paraview.org" <paraview-developers at paraview.org>
> Subject: Re: [Paraview-developers] How to name blocks in multi-block data
> set?
>
> Hi Joshua,
>
> You can do it like this:
>
> dataset->GetMetaData(0)->Set(vtkCompositeDataSet::NAME(), "new name for
> block 0");
>
> Regards,
> Paul
>
> On 25 June 2013 17:47, Joshua Murphy <Joshua.Murphy at lasp.colorado.edu>wrote:
>
>> Hello,
>>
>> I am working on a custom source that pulls data from Nasa's CDA web.  I
>> am downloading data and splitting it into tables (within a multi-block data
>> set) based on space craft data set.  The issue I am running into is that
>> the data block information looks like the image attached:
>>
>>
>> I have been trying to find a way to name the blocks, but I have, as yet,
>> been unable to figure out how to go about doing so.  It is important to
>> name the data sets, as the user  needs to know which space craft instrument
>> the data is from.
>>
>> Could someone quickly point me in the correct direction on how to go
>> about naming the individual blocks of the data set?  DataSet0, DataSet1,
>> etc. are of limited help. :)
>>
>> Thanks,
>> Josh
>>
>> Joshua J. Murphy
>> Computer Scientist
>> Laboratory for Atmospheric and Space Physics
>> University of Colorado, Boulder
>>
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20130701/0a1c9059/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 16467 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20130701/0a1c9059/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 16467 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20130701/0a1c9059/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 11762 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20130701/0a1c9059/attachment-0005.png>