Talk:Data Release 2

Please keep discusion on this page. -- Tdall 11:26, 16 April 2009 (CEST)

Data release policy after DR2
Here is an idea: After robot validation, the so-called health check, for every ten new spectra arrived, the following will happen:
 * VSOP team gets notification of stars up for public release, listing:
 * planned release date (e.g. 14 days into the future)
 * "strangeness score" for each star (see next headline below...)

Once the release is due, the robot will:
 * change the data and star page permissions
 * update wiki front news page
 * update RSS feed (TBD)
 * update on twitter (TBD)
 * send out email alerts (people sign up for these?)
 * send out vsnet alerts (and others - TBD)

Comments welcome --- and $\pi$, tdall 18:14, 6 May 2009 (CEST)

Definition of "strange"...
We aim to find "strange beasts", but what exactly do we mean by that? It must be possible to flag a star as "interesting" or "strange", so the VSOP team can get a heads-up on what might be an interesting object before it goes public (see discussion headline above...).

We could imagine having several criteria, all of which contribute to an overall "strangeness-score". These could be:
 * RV extremes (TBD)
 * SB3 or more
 * broad emission + late spectral type (TBD x 2)

All these criteria will have to be automated, i.e. the robots/scripts will have to automatically test for the criteria and assign a strangeness score. The key word here is "automated"...

Comments please. -- and π, tdall 18:19, 6 May 2009 (CEST)