<div dir="ltr">Timo,<div><br>This merge request should fix this issue:</div><div><br></div><div><a href="https://gitlab.kitware.com/paraview/paraview/merge_requests/354">https://gitlab.kitware.com/paraview/paraview/merge_requests/354</a><br></div><div><br>Thanks for reporting the issue. I also checked to see if there are any other references to POINT_DATA/CELL_DATA that need to be updated. I didn't spot any.</div><div><br></div><div>Utkarsh</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 5, 2015 at 8:54 AM, Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks for pointing that out, Timo. I'll take a look.<span class="HOEnZb"><font color="#888888"><br><br><div>Utkarsh</div></font></span></div><div class="HOEnZb"><div class="h5"><br><div class="gmail_quote"><div dir="ltr">On Fri, Jun 5, 2015 at 5:15 AM Timo Oster <<a href="mailto:timo.oster@ovgu.de" target="_blank">timo.oster@ovgu.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi ParaView Developers,<br>
<br>
I have noticed a problem with using scripts generated with the<br>
coprocessing script exporter for rendering screen shots in-situ. The<br>
script generator generates code for coloring surfaces like so:<br>
<br>
slice1Display.ColorArrayName = ['POINTS', 'temperature']<br>
<br>
This is the 'new' way of specifying the coloring.<br>
<br>
When I add this script to a coprocessor that is executed during a<br>
simulation, I will get an error that stems from this portion of code in<br>
Wrapping/Python/paraview/coprocessing.py (line 381):<br>
<br>
input = rep.Input<br>
input.UpdatePipeline(time) #make sure range is up-to-date<br>
lut = rep.LookupTable<br>
if rep.ColorAttributeType == 'POINT_DATA':<br>
datainformation = input.GetPointDataInformation()<br>
elif rep.ColorAttributeType == 'CELL_DATA':<br>
datainformation = input.GetCellDataInformation()<br>
else:<br>
print 'something strange with color attribute type',<br>
rep.ColorAttributeType<br>
<br>
This portion of code still uses the 'old' way of using<br>
ColorAttributeType and ColorArrayName, and, on top of that, still uses<br>
POINT_DATA and CELL_DATA instead of POINTS and CELLS. The code following<br>
this also uses ColorArrayName in the old way, assuming it is not a list.<br>
If the usage of the old way here is intentional, then somewhere,<br>
something that is supposed to ensure backwards compatibility is not<br>
working correctly.<br>
<br>
The client I'm using for generating the script is the exact same<br>
ParaView version as the server evaluating it.<br>
<br>
I have changed the code in coprocessing.py to use the new way, and<br>
everything now seems to work correctly. However, there might be other<br>
instances in the code that were missed when ColorArrayName was updated.<br>
Perhaps somebody more experienced with the code might want to take a<br>
look at this?<br>
<br>
Regards,<br>
<br>
Timo<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=Paraview-developers" target="_blank">http://markmail.org/search/?q=Paraview-developers</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
</blockquote></div></div></div></blockquote></div><br></div>