- jkadkins's home page
- Posts
- 2018
- 2017
- 2016
- 2015
- 2014
- December (3)
- November (2)
- October (4)
- September (7)
- August (2)
- July (3)
- June (1)
- May (4)
- March (4)
- February (3)
- 2013
- December (2)
- November (3)
- October (3)
- September (4)
- August (2)
- July (3)
- June (1)
- May (2)
- January (1)
- 2012
- My blog
- Post new blog entry
- All blogs
EMC^2 Software Coordinator Yearly Task List
This blog will be continually updated with a list of tasks required for the EMC^2 software coordinator to complete (from the BEMC coordinator point of view). They'll be updated as I do them for the sake of future documentation, and come in no particular order.
1.) Updating geometry for current run. For run14, there were no geometry changes so this was very simple. I suggest emailing an expert (Will or Oleg Tsai) and asking if there are changes and moving forward from there.
2.) Initializing the database timestamp: This is done easily with the help of a macro written by Justin Stevens, bemcCopy.C. This can be found attached below and in the directory /star/u/jkadkins/emcTimeline2014/bemcCopy.C. The timestamps for the two flavors ("ofl" and "sim") will have values for which to initialize the database, and will be emailed to the coordinator list by Jerome before the run (sometime in the winter). For run14, the dates were 2013-12-10 00:00:00 for "sim" and 2013-12-20 00:00:00 for "ofl" (these are typical for every year). A couple of notes about using the macro:
- You must run it twice, once for flavor = "sim" and once for flavor = "ofl"
- You must update the "timeOld" and "timeNew" in the code to the appropriate values. This is using an old table in the database so setting "timeOld" to the first of the year will grab the first entry in the database
- You don't need tables to upload, you'll be copying old tables to new timestamps for reasons of initialization.
- For some reason the code breaks when using "sim" flavor. I'm not sure why, but the job still gets done and the tables are copied.
- There is an "error check" in place to prevent accidential uploading. You must change the "#if 0" to "#if 1" to upload the new tables. Make sure that you've tested that the code works before changing to upload mode! Also, to write the tables you'll need to use the command "setenv DB_ACCESS_MODE write" so that you can write tables and not just read them. Then change back to "#if 0" so next year you wont make a mistake!
- jkadkins's blog
- Login or register to post comments