<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#6600cc">
<font face="Helvetica, Arial, sans-serif">It turns out that's exactly
what's going on ... I have cell-centered data, and even if I do select
the variable, it remains "unavailable", although it does appear to be
available. I'll "cvs up" and make sure I have the fix.<br>
<br>
Thanks.<br>
</font><br>
<a class="moz-txt-link-abbreviated" href="mailto:clinton@elemtech.com">clinton@elemtech.com</a> wrote:
<blockquote cite="mid:200709101229.05536.clinton@elemtech.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator"
content="MS Exchange Server version 6.5.7652.24">
<title>Re: [Paraview] Paraview 3.1.1 - exodus files</title>
<!-- Converted from text/plain format -->
<br>
<p><font size="2">I see that behavior too for element centered
scalars. Even though that part<br>
of the GUI says "Unavailable," they really were loaded and available,
so you<br>
can use them.<br>
<br>
A fix was put it CVS just now so it won't say "Unavailable" anymore.<br>
<br>
Clint<br>
<br>
On Monday 10 September 2007 12:09:33 pm Rick Angelini(CISD/CIV) wrote:<br>
> I have files named exodus_test.exo.00, exodus_test.exo.01 ...<br>
> exodus_test.exo.31 (32 dump files)<br>
><br>
> When I open the directory in V3.1.1, it shows me
"exodus_test.exo.32" ...<br>
> the reader is apparently counting exodus files and giving me a
meta-name<br>
> with a 32 appended to it ....<br>
><br>
> When I load up exodus_test.exo.32, I see the 12 blocks from the
dataset,<br>
> but my scalar variables are all listed as "Unavailable". Even if
I try to<br>
> select one of the scalars (such as volfrac1), the scalar remains<br>
> unavailable.<br>
><br>
><br>
><br>
> Moreland, Kenneth wrote:<br>
> It works fine for me. I just built ParaView 3.1 this morning.
You of<br>
> course have to make sure that the variables are checked off in the
object<br>
> inspector, but that is no different than ParaView 2.X.<br>
> One thing that has changed is that the block id is no longer the
default<br>
> scalar, so that the exodus data will come up with no coloring.
You should<br>
> still see all of the scalars listed under the variable selector
combo box,<br>
> though.<br>
> -Ken<br>
> <br>
><br>
> From: <a class="moz-txt-link-abbreviated" href="mailto:paraview-bounces+kmorel=sandia.gov@paraview.org">paraview-bounces+kmorel=sandia.gov@paraview.org</a><br>
> [<a moz-do-not-send="true"
href="mailto:paraview-bounces+kmorel=sandia.gov@paraview.org">mailto:paraview-bounces+kmorel=sandia.gov@paraview.org</a>]
On Behalf Of Rick<br>
> Angelini(CISD/CIV) Sent: Monday, September 10, 2007 11:33 AM<br>
> To: <a class="moz-txt-link-abbreviated" href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
> Subject: [Paraview] Paraview 3.1.1 - exodus files<br>
> <br>
> Is there a trick to getting Paraview 3.1.1 to read Exodus files?
I can<br>
> load up the data fine in 2.6 ... but I'm not getting any of the
scalars<br>
> loaded in V 3.1.1.<br>
><br>
> On a side note, is there an archive of the email traffic that
shows up on<br>
> this list? I would have liked to have scoured recent email
messages to see<br>
> if there is some info on Exodus files, but don't see a way to do
that.<br>
><br>
><br>
> Thanks.<br>
<br>
<br>
</font>
</p>
</blockquote>
</body>
</html>