Changes between Version 2 and Version 3 of drmsCheckTriggers

Timestamp:

02/11/14 10:45:06 (10 years ago)

Author:

niles

Comment:

--

drmsCheckTriggers

@@ -46 +46 @@
 
 Note that this still does not get the data on disk - but your local DRMS/SUMS database now has knowledge that the data exists offsite. Given that, the JMD
-will be able to download it.
+will be able to download it. Triggers and update functions follow the naming convention :
 
+{{{
+(instrument)_(series)_trg
+(instrument)_(series)_fc
+}}}
+
+To identify triggers for automatically downloading data (writes records into sunum_queue), the convention is :
+{{{
+        trig_update_vso_(shadow table name)
+}}}
+
+Procedures that maintain the VSO shadow table :
+{{{
+        proc_update_vso_(shadow table name)
+}}}
+       
+
+Some functions that mention 'dynamical'. This arises because JSOC store their dates as seconds since an epoch in 1968. The functions have the tables of leap seconds so we can convert to unixtime (technically, it forces conversion to the database internal date type). This facilitates queries like :
+
+{{{
+select (whatever) from aia.lev1 where t_rec_index between dynamical('YYYY-MM-DD') and dynamical('YYYY-MM-DD')
+select dynamical_to_unix(date__obs) from aia.lev1 where recnum in ( ... )
+}}}
+
+These queries may take time, as the tables are big and for the most part, unindexed.
+