[Kst] Re: time display

[Marc-Antoine Miville-Deschenes]

I agree that this is very useful.
For Planck we have timevectors in UT (in seconds).
The most common case for us now is to plot [hh:mm:ss].
Usually we put the date in the toplabel.

Marc-Antoine

On 7-Oct-04, at 5:49 PM, Barth Netterfield wrote:

> Cool!
>
> This is the correct approach I think.
>
> I like the layout of the dialogs.
>
> -Is there a way of using the user's locale to select the default 
> display?  Or
> should just be a sticky default like we do with 'vectorDefaults?'
> -I think there should be an option for 'current locale' as well as the 
> hard
> coded options.
> -Would it be a good idea to use some huristics to set the time 
> interpretation
> default based on the plot ranges (1012004110-1012024110 is almost 
> certainly a
> ctime, not a JD).
> -are there more options that might be useful?
> 	-hh:mm:ss (ie, no date)
> 	-A format which uses 'January' or 'Jan' rather than 01
> -would it be a good idea to be able to select the units of the offset 
> time
> [+200]  (ie, decimal days, decimal hours, etc rather than seconds).  
> Or could
> this be automatically selected.
>
> The offset time approach seems pretty good to me if we are in Date 
> Time mode.
>
> The rule for where [+0] should be: the date/time which has the most 
> zeros
> starting from the LSField.  (ie, 2003/01/00 00:00:00 prefered over 
> 2003/12/31
> 00:00:00, preferred over 2003/12/31 00:00:10).
> This means that where the +0 will go is dependent on how it is being 
> displayed
> (JD may be different than DATE-TIME)
> In Date Time mode, if we are so lucky as to have a field which has 
> 00:00:00
> for time, this could be dropped.
>
> I suspect we are going to be changing this for a while as we see what 
> works
> well and what doesn't.  It is a non trivial problem.
>
> cbn
>
> On October 6, 2004 05:55 pm, Andrew Walker wrote:
>> CVS commit by arwalker:
>>
>> Add the ability to interpret the x-axis values as various time 
>> formats, and
>> display in another time format.
>>
>> This is only a display of the concept at this point and the following
>> issues need to be addressed:
>>
>> * tick positioning
>> * permissible range of data
>> * reported position (for cursor and nearest data point)
>>
>> In all of the above the algorithms use the raw data values, where they
>> should be using/displaying the converted time values.
>>
>> I will await comments before proceeding to fix this issues.
>>
>>
>>   M +545 -115  kst2dplot.cpp   1.275 [POSSIBLY UNSAFE: printf]
>>   M +30 -7     kst2dplot.h   1.113
>>   M +1 -0      kstlegend.h   1.9
>>   M +120 -47   kstplotdialog_i.cpp   1.101
>>   M +231 -166  plotdialog.ui   1.62
>>
>>
>>
>> _______________________________________________
>> Kst mailing list
>> Kst at kde.org
>> https://mail.kde.org/mailman/listinfo/kst
>
>
> _______________________________________________
> Kst mailing list
> Kst at kde.org
> https://mail.kde.org/mailman/listinfo/kst
>
Marc-Antoine Miville-Deschenes
Institut d'Astrophysique Spatiale
tel.: 01 69 85 86 78