#26 X,Y axis units should be configurable per dataset

Feature
closed-fixed
David Benn
Charts (44)
9
2014-08-10
2009-08-14
David Benn
No

Especially in the case of the simple data format, it should be possible to vary the units used on each axis on a per dataset basis. One of the CitizenSky participants (whose name I did not record at the time) suggested this.

This would allow people to generate data from sources other than AAVSO.

In the case of the simple file format, an additional optional initial line could specify this. A concrete proposal is needed.

Discussion

  • David Benn
    David Benn
    2009-08-14

    • summary: X,Y axis unit should b configurable per dataset --> X,Y axis units should b configurable per dataset
     
  • David Benn
    David Benn
    2009-09-07

    I propose that the simple file format be augmented to have an optional first line that describes the name and permissible values of each of the first two columns, currently JD and Magnitude. For example, the first line could be:

    FORMAT:Minutes:\d+,Rads:\d+(.\d+)?

    where two columns are named (Minutes and Rads) and whose values are constrained (via regular expressions) to be integer and real, respectively, permitting files to be validated upon input.

    We could generalise this to permit an arbitrary number of columns, each of which can be described as above. But this would be of little value unless at least some had a-priori meaning. In the context of VStar, that means designating say, the first two columns as X,Y values to be plotted, with all others appearing as information in a dialog box upon clicking such a plotted value, or appearing as values in a table. Such a generalisation may be overkill however.

     
  • David Benn
    David Benn
    2011-05-19

    • summary: X,Y axis units should b configurable per dataset --> X,Y axis units should be configurable per dataset
     
  • David Benn
    David Benn
    2012-01-16

    Another example of this is that observation plugins may read data whose domain is BJD or HJD or some other time unit, as in recent conversation with Kevin Alton.

     
  • David Benn
    David Benn
    2013-07-09

    One approach is for AbstractObservationRetriever for each data source to return time and brightness axis labels or at least the parenthesised portion, e.g. Time (JD, HJD, JD - 2,450,000, ...) or Brightness (magnitude, flux, ...). The Time axis is particularly relevant here. Other plugins ought to be able to change the axis labels also, e.g. if one converts from mag to flux as is considered desirable for eclipsing binary analysis.

     
    Last edit: David Benn 2014-08-02
  • David Benn
    David Benn
    2014-08-02

    This has also arisen in the context of Paul York's Hipparcos observation source plug-in which has time units of BJD(TT). The AbstractObservationRetriever approach makes sense here.

     
  • David Benn
    David Benn
    2014-08-10

    • status: open --> closed-fixed
     
  • David Benn
    David Benn
    2014-08-10

    Implemented in 2.16.3