Chinese SONG and mini-SONG SoftwareXiaomeng LuNational Astronomical Observatories, CAS18 Sep, 2011The 4th Workshop

Chinese SONG SoftwareSONG is a Network Group, each node should act in the same way, so well copy the prototype as many as possible.OS: Debian LinuxInfrastructure: OpenVPN, VLAN, Vmware, PostgreSQLTools: Slony-I, Gluster FS, BaculaMechanism: trigger based on PostgreSQL, daemon, data driveDevelopment Language: Python, C/C++, HTMLReference: 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.

TelescopeAstelcoOpenTCI(Telescope Driver) & OpenTSI(User Interface) based on TPL2 to share prototype codesExtended TPL2 gives more functions for diagnosesThat would be possible and we will make the draft at end of September.Spectrometer & CCDWould use the same design plan and modelOther InstrumentsSuch as Cloud Monitor & Dust Monitor, we will write their drivers, extend database tables and error daemonsImage File(s)Drawing up FITS Head specification, containing enough detailed informationAdditional FunctionsAutomatic pointing calibration -- remember axes position and sky position. if the error is greater than threshold, making point model and replacing the calibration parameters automatically

What to do for Chinese SONG Software

Comparing the difference between prototype and Chinese node, to write correlative drivers, triggers and scripts, etc. Setup the developing and runtime environments, make somebody to be familiar with them Tracking prototype subversion Administrate Chinese node software locally and upload to Danish server after test Quick local data processing, such as lucky image filtering and combining, automatic telescope pointing calibration

mini-SONG Softwaremini-SONG is somewhat different from SONG for their different requirements and design plans.Wide FOVHigh PrecisionLong time termSimultaneity2(or Multi)-ColorSurveyMatch telescope & CCDHigh accuracy pointing (no AGU)Double Tube & CCDRelay between sitesObserve strategy

mini-SONG will use many same factors as SONG:Platform, Infrastructure, Tools, Mechanism, Development languages, Environment instruments

What to do for mini-SONG software: Requirement Analysis Data structure definition Logic definition Setup runtime environment Code & test & documentation

What have been determined: Debian 6.0.2, 64bit PostgreSQL 8.3.15 Python 2.7.2 GNU C++ 4.4.6 WEB interface for client Data drive mechanism

VPNSecure NetworkVLANRemote seems to be localClusterdata exchange between serversSOCKETcommunication in same siteData Drivevaried data drive workflowRemote Maintenancethrough rDesktop or SSH

Content:(1) setup platform(2) design DB(3) Image file path architecture(4) data process(5) WEB interface

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(0~5)Observe Type survey [lucky image]Filter Color B VExposure Time xxxx.xxxExposure Number nSynchronization yes[no]Observe Policy nBegin Date YYYY-MM-DDLife Cycle nnnSubmitters ABCDEF(the followings are object information)Name RA DEC Epoch Priority ObserveType FilterColor ExposureTime Synchronization

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 2011Give evaluation before July 2012Give stable V1.0 before Dec 2012

ThanksFor your attention!