Chinese%20SONG%20and%20mini-SONG%20Software

1
The 4th Workshop
Chinese SONG and mini-SONGSoftware
Xiaomeng Lu National Astronomical Observatories,
CAS 18 Sep, 2011
2
Chinese SONG Software
SONG is a Network Group, each node should act in
the same way, so well copy the prototype as many
as possible.
OS Debian Linux
Infrastructure OpenVPN, VLAN, Vmware, PostgreSQL
Tools Slony-I, Gluster FS, Bacula
Mechanism trigger based on PostgreSQL, daemon,
data drive
Development Language Python, C/C, HTML
Reference IRAF, Sextractor,
But Chinese node is not strictly same to
prototype, we hope the left programs are just
concerned with Hardwares that different from
prototype.
3

• Telescope?Astelco
• OpenTCI(Telescope Driver) OpenTSI(User
  Interface) based on TPL2 to share prototype codes
• Extended TPL2 gives more functions for diagnoses
• That would be possible and we will make the draft
  at end of September.
• Spectrometer CCD
• Would use the same design plan and model
• Other Instruments
• Such as Cloud Monitor Dust Monitor, we will
  write their drivers, extend database tables and
  error daemons
• Image File(s)
• Drawing up FITS Head specification, containing
  enough detailed information
• Additional Functions
• Automatic pointing calibration -- remember axes
  position and sky position. if the error is
  greater than threshold, making point model and
  replacing the calibration parameters automatically

4
What to do for Chinese SONG Software lt1gt
Comparing the difference between prototype and
Chinese node, to write correlative drivers,
triggers and scripts, etc. lt2gt Setup the
developing and runtime environments, make
somebody to be familiar with them lt3gt Tracking
prototype subversion lt4gt Administrate Chinese
node software locally and upload to Danish server
after test lt5gt Quick local data processing, such
as lucky image filtering and combining, automatic
telescope pointing calibration
5
mini-SONG Software
mini-SONG is somewhat different from SONG for
their different requirements and design plans.
Wide FOV High Precision Long time
term Simultaneity 2(or Multi)-Color Survey
Match telescope CCD High accuracy pointing (no
AGU) Double Tube CCD Relay between
sites Observe strategy
6
mini-SONG will use many same factors as
SONG Platform, Infrastructure, Tools, Mechanism,
Development languages, Environment instruments
7
What to do for mini-SONG software lt1gt
Requirement Analysis lt2gt Data structure
definition lt3gt Logic definition lt4gt Setup runtime
environment lt5gt Code test documentation What
have been determined lt1gt Debian 6.0.2, 64bit lt2gt
PostgreSQL 8.3.15 lt3gt Python 2.7.2 lt4gt GNU C
4.4.6 lt5gt WEB interface for client lt6gt Data drive
mechanism
8

• VPNSecure Network
• VLANRemote seems to be local
• Clusterdata exchange between servers
• SOCKETcommunication in same site
• Data Drivevaried data drive workflow
• Remote Maintenancethrough rDesktop or SSH

9
Content (1) setup platform (2) design DB (3)
Image file path architecture (4) data process (5)
WEB interface
10
(No Transcript)
11
Data flow between key points
Schedule is saved as TXT file and submit through
WWW page. The schedule file would be like
following style Site List All device-name
device-name2 device-name3 Priority Level
0(05) Observe Type survey lucky image Filter
Color B V Exposure Time xxxx.xxx Exposure
Number n Synchronization yesno Observe Policy
n Begin Date YYYY-MM-DD Life Cycle
nnn Submitters ABCDEF (the followings are object
information) Name RA DEC Epoch Priority
ObserveType FilterColor ExposureTime
Synchronization
12
FITS Head will include (1) Standard (2)
Object(Schedule No, Object name, RA DEC,
Frame) (3) Filter(Photometry system, Color) (4)
Mount site(name, geography) (5)
Telescope(diameter, f-ratio, focus) (6) CCD
Camera(resolution, pixel size, OVERSCAN,
cool-set, cooler) (7) Weather(Air Pressure,
Temperature, Humidity) (8) Pointing(Alt-Azimuth,
RA-DEC) (9) Exposure(Readout port, Readout speed,
Readout noise, Gain, DATE-OBS, TIME-OBS, EXPTIME,
TIME-END)

• We Hope
• Give V1.0 design documentation during Oct 2011
• Give evaluation before July 2012
• Give stable V1.0 before Dec 2012

13
Thanks For your attention!