Changes between Version 8 and Version 9 of UltracamApi
- Timestamp:
- Jan 24, 2008 9:51:37 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UltracamApi
v8 v9 17 17 When designing '''UCam''' there were several goals in mind, conclusions that were 18 18 based on extensive use of earlier 19 , VxWorks based SDSU systems. The main goals we hoped to achieve were;19 ,!VxWorks based SDSU systems. The main goals we hoped to achieve were; 20 20 21 21 Simple, effecient real-time layer:: 22 22 We wanted the real time 23 layer to be as simple as possible. Previous systems had used <nop>VxWorks23 layer to be as simple as possible. Previous systems had used !VxWorks 24 24 throughout and bug fixes had been applied at all levels. Real-time layers are 25 25 difficult to code and test, and we felt that by minimising the compelxity and … … 208 208 209 209 === XML usage in Ultracam === 210 The re are, conceptually, three levels of XML files in Ultracam;210 The XML files in Ultracam are used to store (almost) all information about the system, from the lowest level DSP executable code to user comments about the data sets. The standard set up of Ultracam includes three levels of files; 211 211 212 212 Low level files:: … … 218 218 Intermediate files:: 219 219 these are hand written, and are used to apply validation to variables using '''condition_check''' tags and to describe the data format using 220 an '''application_data''' section. 220 an '''application_data''' section. There are also ancillary files which describe the SDSU hardware, telescope details etc. 221 221 222 222 Top level files:: 223 223 these are the files that get sent to the system by an interface. They contain '''set_parameter''' tags (in a '''configure_XXX''' section) and 224 224 (potentially) a '''user''' section 225 226 227 It should be noted that this three layer structure is entirely arbitrary - since the XML files reference each other (see XML Message Execution below) Ultracam could use 1 or more files. Three levels just seems to be optimal from a human point of view. 228 229 == XML Message Execution == 230 The following details the conceptual order of processing when an XML message is sent to one of the servers (camera or filesave). 231 232 225 233 226 234