MediaWiki API result
This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
"batchcomplete": "",
"continue": {
"gapcontinue": "Run_Group_B",
"continue": "gapcontinue||"
},
"warnings": {
"main": {
"*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
},
"revisions": {
"*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
}
},
"query": {
"pages": {
"185": {
"pageid": 185,
"ns": 0,
"title": "Recent Changes and Current Issues",
"revisions": [
{
"contentformat": "text/x-wiki",
"contentmodel": "wikitext",
"*": "\nmoved to run group wiki (RG-K)"
}
]
},
"37": {
"pageid": 37,
"ns": 0,
"title": "Run Group A",
"revisions": [
{
"contentformat": "text/x-wiki",
"contentmodel": "wikitext",
"*": "= Shift Documentation =\n<!--####################################### SHIFT DOCUMENTATION ########################################-->\n{| {{TableStyle1}}\n\n| valign=top |\n<!--==={{#switchtablink:Phone Numbers|'''Phone Numbers'''}}===-->\n===[http://www.jlab.org/Hall-B/shifts Shift Schedule]===\n===[https://logbooks.jlab.org/checklists/151 Shift Checklist] ===\n===[https://accweb.acc.jlab.org/hco/readiness Hot Checkout]===\n===[https://bta Beam Time Accounting]===\n* See guidance for BTA in '''[https://accwiki.acc.jlab.org/pub/SWDocs/BeamTimeAccounting/Machine_Time_Accounting_User_Guide.pdf Beam Time Accounting User Guide]'''.\n<!-- ===[https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc#CLAS12_Operations_Documentation Operations Documentation]=== -->\n\n| valign=top |\n===Manuals===\n* [https://clasweb.jlab.org/wiki/images/c/c2/Band_om.pdf BAND]\n* [https://clasweb.jlab.org/wiki/images/4/4d/Beamline_manual.pdf Beamline]\n* [https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf CND]\n* [https://clasweb.jlab.org/wiki/images/c/c1/Shift_Worker_Manual_January_2018.pdf Cryo-Target]\n* [https://clasweb.jlab.org/wiki/images/0/0f/Ctof_manual.pdf CTOF]\n* [https://clasweb.jlab.org/wiki/images/a/ab/Opman_master.pdf DAQ]\n* [https://clasweb.jlab.org/wiki/images/b/b2/Drift-chamber-operating-procedure.pdf DC]\n* [https://clasweb.jlab.org/wiki/images/a/a2/Ec_manual.pdf ECAL]\n* [https://clasweb.jlab.org/wiki/images/3/3b/FT-Manual.pdf FT]\n* [https://clasweb.jlab.org/wiki/images/b/b0/Ftof_manual.pdf FTOF]\n* [https://clasweb.jlab.org/wiki/images/f/f1/HTCC_MANUAL.pdf HTCC]\n* [https://wiki.jlab.org/clas12-run/images/d/d2/Ltcc_manual.pdf LTCC]\n* [https://clasweb.jlab.org/wiki/images/a/ad/Documentation_Shifters_MVT.pdf MVT]\n** [https://wiki.jlab.org/clas12-run/images/b/bf/MVT_for_Dummies.pdf MVT turn on procedure]\n* RICH: [https://clasweb.jlab.org/wiki/images/e/ea/RICH_Manual.pdf expert] [https://wiki.jlab.org/clas12-run/images/d/d9/RICH_Controls_mc.pdf novice]\n* [[Media:clas12controls_shift.pdf|Slow Controls]]\n* [https://clasweb.jlab.org/wiki/images/d/dc/Hall_B_Solenoid_Power-Up_and_Power-Down_Procedure.pdf Solenoid Power-Up and Power-Down Procedure]\n* [https://clasweb.jlab.org/wiki/images/9/96/Svt_operation_manual_v1_1.pdf SVT]To switch on SVT see [https://logbooks.jlab.org/files/2018/10/3615766/svt_problem_solving_0.pdf SVT short]\n* [https://clasweb.jlab.org/wiki/images/d/d6/Hall_B_Torus_Power-Up_and_Power-Down_Procedure.pdf Torus Power-Up and Power-Down Procedure]\n\n| valign=top |\n===Procedures===\n* [[Media:estab_beam.pdf|Establishing Physics-Quality Beam]]\n* [[Media:clas12moller.pdf|Performing Møller Runs]]<!--** [[Media:moller.pdf|Old, Expert Møller]]-->\n* [[Media:HarpScanManual.pdf|Performing Harp Scans]]\n* [https://wiki.jlab.org/hps-run/images/0/0c/Accessing_the_tunnel.pdf Tunnel/Hall Access]\n<!--* [https://clonwiki0.jlab.org/wiki/index.php/DAQ/Online_Quick_Reference <span style=\"color:red;\"><b>DAQ Quick Reference/Recovery</b></span>] -->\n\n| valign=top |\n===JLab Logbooks===\n<font size=3>\n* [https://logbooks.jlab.org/book/elog MCC]\n* [https://logbooks.jlab.org/book/halog Hall-A]\n* [https://logbooks.jlab.org/book/hblog Hall-B]\n* [https://logbooks.jlab.org/book/hclog Hall-C]\n* [https://logbooks.jlab.org/book/hdlog Hall-D]\n</font>\n\n|}\n\n= Phone Numbers =\n\nIf calling local numbers (with area code prefix '''757''') from the counting room dial '''9+[last 7 digits]'''. To call other area codes dial '''91+[10 digit number]'''\n\n<!--####################################### PHONE NUMBERS #############################################-->\n{{PhoneNumbers}}\n[https://wiki.jlab.org/clas12-run/index.php?title=Template:PhoneNumbers&action=edit Click Here] to edit Phone Numbers. Note, you then also have to [https://wiki.jlab.org/clas12-run/index.php?title=Run_Group_A&action=edit§ion=9 edit this page] to force a refresh.\n\n<!-- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATE-->\n\n= Short Term Schedule =\n<center><font color=blue size=4>\n''' CLAS12 Run Group A, Spring 2019 </font> '''<br>\n''' Beam energy 10.2 GeV (5 pass) '''<br>\n''' Important: Document all your work in the logbook! '''<br>\n''' Remember to fill in the [https://docs.google.com/spreadsheets/d/1g2L33OKvKVFMq3MNGYAuS02l0CCKomPbDm8iULLhueY/edit#gid=0 run list] at the beginning and end of each run\n</center>\n\n== RC: Nick Markov ==\n* (757) 575-7540 \n* 9 575 7540 from Counting Room\n* [mailto:markov@jlab.org markov@jlab.org]\n\n== PDL: Maurizio Ungaro ==\n* (757) 876-1789 \n* 9 876-1789 from Counting Room\n* [mailto:ungaro@jlab.org ungaro@jlab.org]\n\n{| {{TableStyle1}} \n\n| valign=top width=50% |\n\n== <font color=blue>''' Run Plan: April 8-15, 2019'''</font>==\n(Last updated: April 12th, 2019 @ 19:00)\n\n<b>DAQ config: PROD66; Trigger file: rga_v2.trg</b>\n<!--\n* When the Hall is in beam permit:\n** Energize the tagger \n** The liquid-hydrogen target should be full \n** All detectors should be off (except for MVT in safe mode).\n** The solenoid should be at -100% field (2416 A) and the torus should be at -100% field (3770 A negatives inbending).\n\n* When beam is available:\n** Establish the beam on the tagger yoke dump (see instructions [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]). \n** Perform 2C21 and 2C24 harp scans (follow instructions [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf])\n\n* If beam is acceptable:\n** Degauss the tagger magnet\n** Set the FSD thresholds(upstream 2000, midstream 2000, downstream 500000, BOM 35000, 5.0 ms dwell time)\n** Send 5 nA beam to Faraday cup and make sure beam is clearly seen on the downstream viewer and the halo counter rates are acceptable.\n** Perform 2H01 harp scan (follow instructions [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]).\n\n* After beam is established on FC and the beam profile is acceptable, turn on the CLAS12 detectors.\n\n* Take low current production at 10 nA for 4 hr.\n-->\n<!--\n* Take production data at 50 nA in 4 hr runs!\n\n*Note: <font color=red>DO NOT IGNORE</font> unsafe FSD masking alarm! Follow alarm guidance.\nTake production data at 50nA for 4 hr until he swing shift. \n\nStarting from the swing shift,\n\n* Take 2 hours random trigger run at 10 nA using rgb_v9_1_faraday_noprescale.trg trigger file and beam blocker removed. Expect 10 kHz DAQ rate. Change the DAQ alarm limits by going to DAQ /CLAS12 Trigger /Menu /Alarm Settings Expert/ Set All Normalized Rate Limits when the beam and rates are stable.\n\n* Take 20 minutes random trigger run at 50 nA using rgb_v9_1_presxcale_3.trg trigger file and beam blocker removed. Expect 15 kHz DAQ rate. Change the DAQ alarm limits by going to DAQ /CLAS12 Trigger /Menu /Alarm Settings Expert/ Set All Normalized Rate Limits when the beam and rates are stable.\n\n* Take 6 hours low luminosity run at 10 nA with the beam blocker in and rga_v2.trg trigger. Change the DAQ alarm limits by going to DAQ /CLAS12 Trigger /Menu /Alarm Settings Expert/ Set All Normalized Rate Limits when the beam and rates are stable.\n\n* At 2 am empty the target and run 150 nA beam until the beam is taken away with rga_v2.trg and the beam blocker in. Change the DAQ alarm limits by going to DAQ /CLAS12 Trigger /Menu /Alarm Settings Expert/ Set All Normalized Rate Limits when the beam and rates are stable. Change the BTA accounting limits in the Beamlin/BTA config (replace the upper limit with 160 nA). \n\n\nThe beam is expected to be back around 3-15 pm on Monday, April 8'th. \nChange HWP to \"OUT\" and take a Moeller run.\nAfter establishing the physics-quality beam (follow the procedure outlined in https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf) take production data at in 4 hours runs at 50 nA, DAQ config: PROD66; Trigger file: rga_v2.trg.\nOn the Torus/Magnet power Suppy monitor torus MPS Control Comm \n-->\n\nTake production data at in 4 hours runs at 50 nA, DAQ config: PROD66; Trigger file: rga_v2.trg.\n\nOn the Torus/Magnet power Suppy monitor torus MPS Control Comm light. It should be green. If not, contact Magnet group.\n\n<b>Pay special attention to scalers of the PCAL and FTOF in sector 5 (under scalers/CLAS12 Forward Carriage/Sector 5) and make sure there are no dead channels in PCAL and FTOF. Also, when looking at monitoring histograms, pay special attention to sector 5 for the same detectors.</b>\n<b> We had a problem with scalers in sector FTOF 4 which went out. Please monitor it very closely (along with sector 5) and if anyhitng happen contact Sergey (DAQ expert) right away.</b>\n\n<font color=red>\nAfter the beam is off at 6 am on Monday morning:<br>\n- turn the HTCC HV off;<br>\n- turn the LTCC HV off;<br>\n- turn the FT HV off (only HV!);<br>\n\n- <b>Do Not turn BAND HV Off</b>.<br>\n- <b>Do Not turn EC/PCAL HV Off</b>.<br>\n- <b>Do Not turn CTOF and FTOF HV Off</b>.<br>\n- <b>Do Not turn RICH HV Off</b>.<br>\n- <b>Do Not turn SVT HV Off</b>.<br>\n\n</font>\n\n*Note: <font color=red>DO NOT IGNORE</font> unsafe FSD masking alarm! Follow alarm guidance.\n\n\n<font color=red>'' [https://clas12mon.jlab.org/mon12/histograms/?reference=3630375 Compare the monitoring histograms from clas12mon to the reference and troubleshoot as needed.] ''</font>\n\n<b><font color=red> At the end of each run, follow the standard DAQ restart sequence ''' <br>\n''(Note, this might be different from the instructions coming up on RunControl.)''\n\n* \"end run\", \"cancel\", \"reset\" \n* if the run ended correctly:\n** '''\"download\", \"prestart\", \"go\"'''\n* if the run did not end correctly or if any ROCs had to be rebooted:\n** \"configure\", \"download\", \"prestart\", \"go\"\n</font></b>\n\n== <font color=blue>''' References and Standards:'''</font>==\n''(last update March 27, 2019 @ 8:53 a.m.)''\n\n<b> Restoration of Beam to Hall B</b>\n\n<b> Nominal Beam Positions </b>\n*2H01, X: +3.0 mm, Y: -1.0 mm\n*2C24, X: +0.25 mm, Y: 0.35 mm\n\n<b> FSD Thresholds </b>\n* Upstream: 2000 Hz\n* Midstream: 2000 Hz\n* Downstream: 500000 Hz\n* BOM: 35000\n\n<b> Reference Harp Scans for Beam on Tagger Dump: </b> 2C21 [https://logbooks.jlab.org/entry/3672101], 2C24 [https://logbooks.jlab.org/entry/3672102]\n\n<b> Reference Harp Scans for Beam on Faraday Cup: </b> 2H01 [https://logbooks.jlab.org/entry/3672120]\n\n<b> Reference Monitoring Histograms</b> 5 nA production trigger [https://logbooks.jlab.org/entry/3672274], 50 nA, production trigger [https://logbooks.jlab.org/entry/3672136] (to be updated) \n\n<b> Reference Scalers and Halo-Counter Rates: </b> \n* Well-tuned CW beam on FC, Full LH2 target, CLAS12 ON: 5 nA [https://logbooks.jlab.org/entry/3672117], 50 nA [https://logbooks.jlab.org/entry/3672129] \n* Well-tuned CW beam on FC, Empty Target, CLAS12 OFF: 5 nA [https://logbooks.jlab.org/entry/3649436]\n* Well-tuned beam during Moller run [https://logbooks.jlab.org/entry/3649364]\n* Well-tuned beam on Tagger Dump at 5 nA during harp scans: [https://logbooks.jlab.org/entry/3649358] \n* Reference FTC histogram for 5 nA running: [https://logbooks.jlab.org/entry/3665122]\n\n<b> SVT acceptable currents: </b> 1 uA \n\n| valign=top |\n\n==<font color=blue>''' General Instructions''':</font>==\n\n* The main lights in the Hall (dome lights) and the Forward Carriage lights are being kept off because of light leaks affecting some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall. Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cooldown.\n* Do not run more than 30 minutes above 30 nA with 5-pass beam without the beam blocker in front of Faraday cup. Put beam blocker in for long running at high currents for 5 pass operations.\n* Turn DC HV off only for beam tuning; if no beam is available or when beam is stable, keep them on even if you are not taking data.\n* In case of loss of communication with IOCBTARG, follow instructions at https://logbooks.jlab.org/entry/3502218\n* With any issue contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem.\n* Check for and read any comments to log-book entries made during your shift.\n\n'''Once Per Day (on day shift):'''\n* Complete RICH recovery procedure - see Note: 14 below\n\n'''Every Shift:'''\n* Follow run plan as outlined by RC\n* If any concern about beam stability, ask MCC if orbit locks are on (they should be).\n* Keep shift summary up to date in HBLOG. Record all that happens.\n* Document any beam condition change and send scaler GUIs to HBLOG\n* [https://bta.acc.jlab.org Fill out BTA] hourly. Click \"Load from EPICS\" to automatically fill the left side.\n* Upload spectra from clas12mon at begin and end of shift and cross-check with reference spectra\n** Reset clas12mon every ~2 hours and inspect spectra\n* Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]\n* Monitor the SVT Slow Controls status, post plot of current stability in the HBSVT elog once per shift.\n\n'''Every Run:'''\n\n*Log screenshots of:\n** main scaler GUI display \n** Trigger rate gui\n** Beam strip charts\n** FTC scalers\n* Fill out the run info in [https://docs.google.com/spreadsheets/d/1NY1GNIZXPtpB9u4QwP6eNRSrvDkCzFmhQg5RR3V3j7E/edit#gid=0 run list] at the beginning and at the end of each run.\n* <b> When checking the ECAL response, make sure to look at the histograms for each sector by using the sector buttons at the bottom of the clas12mon window - if adcecal* or/and adcpcal* ROC crashes, there will be no alarm and the histograms are the way to notice this issue. \n* Same holds for FT.</b>\n\n|}\n\n* '''Note 1: Be very mindful of the background rates in the halo counters, rates in the detectors, and currents in the SVT for all settings to ensure that they are at safe levels.'''\nThe integrated rates on the upstream counters have to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and the rates on the midstream counters have to be in the range 10-20 Hz (acceptable up to 50 Hz) @50 nA. Counting rates in the range of hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.\n\n* '''Note 2: FTOF HVs: The goal is to minimize the number of power cycles of the dividers.\n** should be turned off during the initial beam tuning down to the Faraday Cup after CLAS12 has been off for a long shutdown, when doing a Moller run, when doing harp scans, or if there is tuned/pulsed beam in the upstream beamline.'''\n** should be left on after an initial beam tune has been established and if there are only minor steering adjustments and \u201ctweaks\u201d being made.\n** if shift workers have doubts what to do with the HVs, they can always contact the TOF on-call expert for advice.\n\n* '''Note 3: In case of a Torus and/or Solenoid Fast Dump do the following:\n*# Notify MCC to request beam OFF and to drop Hall B status to Power Permit\n*# Call Engineering on-call\n*# Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the \"Notify\" field add Ruben Fair, Probir Goshal, Dave Kashy and esr-users@jlab.org \n*# Notify Run Coordinator\n*# Turn off all detectors'''\n\n*'''Note 4: When beam is being delivered to the Faraday Cup:'''\n*# the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state <font color=red>UNMASKED</font>\n*# No changes to the FSD threshold should be made without RC or beamline expert approval\n\n*'''Note 5: Any request for a special run or change of configuration has to be approved by the RC & documented'''\n\n*'''Note 6: Carefully check the BTA every hour and run the script <font color=red>btaGet.py</font> to print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.'''\n\n*'''Note 7: Reset CLAS12MON frequently to avoid histogram saturation. If CLAS12MON is restarted change MAX scale to 10 (default is 5) for DC normalized occupncy histograms. This would prevent them from saturation. See log entry [https://logbooks.jlab.org/entry/3667416]'''\n\n*'''Note 8: Shift workers must check the occupancies! Use this tool to compare to previous runs: [https://clas12mon.jlab.org/mon12/histograms/?reference=3650729]'''\n<!--[https://clas12mon.jlab.org/mon12/histograms/?reference=3621580]'''-->\n\n*'''Note 9: When you have to turn the whole MVT off, do not press \"All HV OFF\": Instead go to 'Restore settings' from the MVT overview screen:\n*# SafeMode.snp for beam tuning and Moeller runs\n*# MV_HV_FullField.snp for full solenoid field\n*# MV_HV_MidField.snp wgeb solenoid < 4T\n'''\n*'''Note 10: Check the vacuum periodically, make sure vacuum is not higher than 5e-5 '''\n\n*''' Note 11: Always reset the CFD threshold after all power off/on on the CND CAMAC crate''' \nAfter the CAMAC crate (camac1) holding the CND CFD boards is switched off for any reason, it is mandatory to reset the associated thresholds typing the\nfollowing command from any clon machine terminal: $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0\n\nIf this command is failing and the crate is not responding, reboot it as follows: roc_reboot camac1\n\n*'''Note 12: ''' Shift workers should anyway check routinely scalers to verify they update correctly and make a logbook entry if anomalies are observed after starting a new run.\n\n*'''Note 13: To solve common SVT issues see https://logbooks.jlab.org/entry/3615766'''\n\n*'''Note 14:''' \nFor RICH recovery procedures, please see Log entry https://logbooks.jlab.org/entry/3562273. This would apply in the cases of 1. DAQ crash: rich4 is not responding or 2. RICH alarms (LV,missing tile, temperature etc). If it does not work or you are uncertain about what to do, contact the RICH expert on call. <u>Please, note </u> that missing tiles typically occur due to lost communication. Keep in mind that the recovery procedure will kill DAQ. If DAQ is running for other purpose, rather than data taking (for which the RICH acceptance would be important) do not initiate the recovery procedure. \n** The most critical parameter for RICH is the temperature of the photosensors. If the temperature rises above limits, an interlock will automatically turn the RICH HV and LV. If this happens, notify the expert on call and keep taking data without RICH.\n\n*'''Note 15:''' Asymmetry on FTCal ADC Scalers: If the beam current is 5 - 10 nA, and the observed asymmetry is out of specs, i.e. > +-2.5%, check (1) that the beam position is according to specs, (2) the response of the rest of CLAS (compare the scalers of FTOF, CTOF, ECAL, etc. from the Scalers GUI to the reference for that current, as posted above). If positions and other detectors do not show any anomalies, keep running. The ADC scalers require at least ~15 nA for a reliable response.\n\n*'''Note 16:''' If ROC mmft1 is 100% busy: power cycle FTT LV (FT->FTT Overview, HV stays ON), roc_reboot mmft1, wait until it reboots (ssh mmft1 to verify). If the first LV recycle/mmft1 reboot doesn\u2019t work call FT expert\n\n= Monitoring =\n<!--####################################### MONITORING ################################################-->\n{| {{TableStyle1}}\n| valign=top |\n===Webcams===\n* [http://hallbcam06.jlab.org/ Faraday Cup Beam Viewer]\n* [http://cctv1.jlab.org Tagger Beam Dump Viewer]\n<!--* [http://cctv12.jlab.org CND/CTOF Ammeter]\n* [http://cctv7.jlab.org FTOF/ECAL Ammeter]-->\n* [http://hallbcam02.jlab.org Hall Fisheye]\n* [http://cctv11.jlab.org Saclay Cryotarget]\n\n| valign=top |\n===Manuals===\n*[https://wiki.jlab.org/clas12-run/images/c/c9/CedManual.pdf CED Manual]\n*[https://wiki.jlab.org/clas12-run/images/f/fd/CLAS12Mon_documentation.pdf MON12 Manual]\n*[https://wiki.jlab.org/clas12-run/images/a/ae/Online_shifts.pdf off-line Manual]\n\n| valign=top |\n===Epics on the web===\n* [https://hallbopi.jlab.org/webopi3.3/w Hall B WebOPI] (CUE Login)\n* [https://epicsweb.jlab.org Accelerator] (CUE Login)\n\n|}\n\n== Fall 2018 Run ==\n{| {{TableStyle1}}\n| valign=top |\n[[Image:Fall2018_charge.jpg|fall2018_charge.jpg|700px]]\n\n| valign=top |\n[[Image:moller_rg_a_fall.jpeg|500px]]\n|}\n\n== Spring 2018 Run ==\n\n{| {{TableStyle1}}\n| valign=top |\n[[Image:chart.jpeg|chart.jpeg|700px]]\n\n| valign=top |\n[[Image:moller_measurement_rg-a.jpg|500px]]\n|}\n\n= Useful Links =\n<!--####################################### USEFUL LINKS ### #############################################-->\n{| {{TableStyle1}}\n| valign=top |\n===Hall-B===\n* [https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc Operation Safety Procedures]\n* [https://wiki.jlab.org/clas12-run/index.php/Engineering_Run Engineering Run Wiki]\n* [https://clasweb.jlab.org/wiki/index.php/Engineering_Run_Analysis Engeineering Run Analysis Wiki]\n* [https://clasweb.jlab.org/wiki/index.php/Run_Group_A Run Group A Analysis Wiki]\n* [http://clasweb.jlab.org/rcdb RCDB]\n* [https://clas12mon.jlab.org/ CLAS12 mon page]\n* [https://clas12mon.jlab.org/mon12/histograms/?reference=3630375 Comparison between mon12 histograms (reference in 1st column compared to last entries)] \n* [https://clas12mon.jlab.org/datasize/ Accumulated datasize]\n* [https://clas12mon.jlab.org/charge/ Accumulated charge]\n\n===Run lists===\n*[https://docs.google.com/spreadsheets/d/1NpojoOi7_gTt_abxgKoHBlofOL7iNWDrtYuiOJ1zoMw RGA Fall 18 run list]\n* [https://docs.google.com/spreadsheets/d/1j6UMJsId8VlsY00dg9Vqm0wmEJZLWVZlsBS-aL49xxw RGA Winter 18 run list]\n* [https://docs.google.com/spreadsheets/d/1frfBlq51qDXZD6fW5rcRefNXSGdVvdMozKUlAVNoUGc ER run list]\n| valign=top |\n===Accelerator===\n* [http://accboard.acc.jlab.org Accelerator Whiteboard]\n* [http://opweb.acc.jlab.org/CSUEApps/bta03/pd_shiftplan_history.php Program Deputy Shift Plans]\n* [http://opweb.acc.jlab.org/internal/ops/ops_webpage/run_coord/runcoord_form.php?action=main Run Coordinator Reports]\n* Accelerator daily meetings notes (by Mauri) [https://www.evernote.com/pub/maureeungaro/pdldaily]\n| valign=top |\n===Bluejeans meetings===\n* [https://bluejeans.com/230805731 Daily Run meeting] 230805731\n|}\n\n\n<headertabs/>\n__NOEDITSECTION__\n__NOTOC__\n{| {{TableStyle1}}\n| valign=top style=\"text-align:center\"|\n[[Image:clas12design.png|500px]]\n|}"
}
]
}
}
}
}