Hi John,<br><br>Glad you got the bug fixed. As far as I can tell, ParaView has now been bug-free for 3 years so I knew it must have been with your code :)<br><br>I can't say for sure but I would think that you'd want to add in the vtkGhostLevel array. The trivial producer that's used to inject the data object into the pipeline probably isn't smart enough to pass that information along yet though. This is something which I've been wondering for a while but haven't gotten around to looking into deeper. It will probably be a bigger issue when we get the live-data working with coprocessing such that people can interact with the data coming out of their simulation code through the coprocessing library. Utkarsh is spending time on that now so someone is going to have to figure out that answer fairly soon. I'll put it on my list of things to do but if you want to take charge of it, I won't complain!<br>
<br>As for the scalar bar error dialogue, I'm not getting it on my machine so I'm not sure how it's coming up much less how to get rid of it. I'd be more than happy to help you get rid of it though once I get more information.<br>
<br>Another thing -- have you looked at CMake's FortranCInterface stuff for automatically mangling the C++ functions to match up with Fortran? It should make it such that you don't have to do the machine dependent mangling yourself. An example is at ParaView/CoProcessing/Adaptors/FortranAdaptors if you haven't checked it out yet.<br>
<br>Andy<br><br><br><br><div class="gmail_quote">On Tue, Jan 10, 2012 at 6:59 AM, Biddiscombe, John A. <span dir="ltr"><<a href="mailto:biddisco@cscs.ch">biddisco@cscs.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-GB">
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">Andy<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">Everything is working ok now. I’m glad that you are far away, because you may want to throw something heavy at me.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">I found that my main problem was that I passed an array of real(4) from fortran to use for the grid spacing and cast them to double* in my adaptor, this caused
some ridiculous numbers to be used for the grid and the python script was basically aborting without doing anything – hence the lack of png output (and no error messages either). Of course all my print statements were in the fortran side to check that the
values were correct so I didn’t catch it for ages.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">Anyway. All seems fine now.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">New Question :
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">I am padding my imagedata pieces with one ghost cell on each side. Contouring etc works fine and pieces abut seamlessly, but for general safety, should I add
a vtkGhostLevel array to my pointdata to ensure that other filters I might add later don’t make data in these regions visible?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">(I didn’t look to see if there is an example anywhere that does this).<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">thanks<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">JB<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">PS. When I add a scalar bar to the display, the script displays this error on the first timestep. Quite annoying – is there anything I can set to true/false
to make it go away.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><img src="cid:image001.png@01CCCF97.857A0700" height="259" width="487"><u></u><u></u></p>
</div>
</div>
</blockquote></div><br>