This issue has been addressed in git-master. The following commit
explicitly sets the locate to "C".
commit cd1b14208b79b8c7773c4bbc10eaf25c680b65c5
Author: Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
Date: Fri Jun 4 13:51:23 2010 -0400
setlocale to avoid locale related numeric issues.
This now affects all executables, not merely Qt-based ones.
Utkarsh
2010/9/16 Aurélien Marsan <aur.mar...@gmail.com>:
> So this is a typically French problem... ! Thank you Joelle for the
> information, it works fine now.....
> And so not having to do the export each time I lauch Paraview, I preferred
> to change the language of my system in English.
>
> But I'm glad I noticed this, before making too many screen-shots... !
>
> Just a word for the paraview developpers : maybe it could be usefull to
> display an error message when the format of floats in a formula is not
> consistent with that of the system ? ..... Or maybe the format of numbers in
> Paraview should not depend on the system language ?
>
> Regards,
>
> 2010/9/15 Joelle Caro <joelle.c...@ec-lyon.fr>
>>
>> Aurelien,
>>
>> I have similar problem with the calculator in ParaView version 3.8.0.
>>
>> I do have to set "export LANG=C" before running paraview, as my system is
>> set up to use language for which decimal is "," and not "."
>>
>>
>>
>> JC
>>
>>
>>
>>
>>
>>
>> > No, it seems that it doesn't depend on the type of data. (I've tried
>> > with
>> > structured bloc and poly data)
>> >
>> > I tried with the binary version 3.8 too... same effect.
>> > I will try with the 3.8.1, but I think I will have to replace all the
>> > dots
>> > by comas.
>> >
>> > Le 15 septembre 2010 16:41, Adriano Gagliardi <agaglia...@ara.co.uk> a
>> > ?crit
>> >
>> > > I tried it with a vtkPolyData and vtkUnstructuredGrid input within
>> > > ParaView 3.8.0 and it worked fine. Is it just with a multiblock
>> > > data-set
>> > > you are having issues?
>> > >
>> > >
>> > > ===================================
>> > >
>> > > Adriano Gagliardi MEng PhD
>> > > Business Sector Leader
>> > > Computational Aerodynamics
>> > > Aircraft Research Association Ltd.
>> > > Manton Lane
>> > > Bedford
>> > >
>> > > Tel: 01234 32 4644
>> > > E-mail: agaglia...@ara.co.uk
>> > > Url: www.ara.co.uk
>> > >
>> > >
>> > > ------------------------------
>> > > *From:* paraview-boun...@paraview.org [mailto:
>> > > paraview-boun...@paraview.org] *On Behalf Of *Aur?lien Marsan
>> > > *Sent:* 15 September 2010 15:36
>> > > *To:* Dave Partyka
>> > > *Cc:* Paraview
>> > > *Subject:* Re: [Paraview] ... something really weird.... dependance
>> > > with
>> > > matplotlib version ?
>> > >
>> > > ... I don't understand anything at all now...
>> > >
>> > > From a same MultiBlockDataSet, doing this in Paraview through a
>> > > programmable filter, and in pvpython, I don't get the same result ...
>> > > !
>> > >
>> > > from paraview import vtk
>> > >
>> > > i = self.GetInput()
>> > >
>> > > b = i.GetBlock(1)
>> > >
>> > > c = vtk.vtkArrayCalculator()
>> > >
>> > > c.SetInput(b)
>> > >
>> > > c.SetFunction('1.4')
>> > >
>> > > c.SetResultArrayName('test')
>> > >
>> > > c.Update()
>> > >
>> > > print c.GetOutput().GetPointData().GetArray('test').GetTuple1(1)
>> > >
>> > > in pvpython ---> 1.4
>> > > in paraview ---> 1.0
>> > >
>> > > Could someone reproduce this ?
>>
>
>
> _______________________________________________
> 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
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/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
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
