| Miniproposals | ||||||||||
|
| Operators | |
| Session leader(s): | Steve Wolfe |
| Physics operator(s): | Steve Wolfe |
| Engineering operator(s): | Andy Pfeiffer |
| Engineering Operator Run Comment |
| automatically entered by signon - please replace with real comment |
| Session Leader Plans |
| Physics Operators Plans |
| Entered: Jun 21 2009 11:15:01:650AM |
| Author: Steve Wolfe |
| Physop plan and engineering setup for Monday 6/22/2009
If the TF scanner is available we will complete power testing with TF tests and proceed to attempt to get plasma. If not, we will start the first part of MP#555 PF Error Field Evaluation and Compensation, which calls for long single supply PF pulses under DPCS control. Note that depending on results, it may be necessary to modify the EF3 and EF4 bus connections to pulse the upper and lower coils independently, as was done on 1030717. It would also be necessary to change the A-coil taps; see detailed physop run plan below. PO: wolfe Run begins at 09:00 and ends at 17:00 ----------------- ************************************************************************* Engineering Setup for Option #1: TF tests followed by plasma (see next PO_PLAN entry for Option#2: MP#555 PF error field evaluation) ----------------- Power systems as on: ? Up to EngOps for TF test When we start trying for plasma, power system as on 1080523011 Acoil: +Dtop -Dbot -Jtop +Jbot (standard) Hybrid Enabled Gas setup: Fill B-Top with 6 psi D2 Hybrid enabled (PG4) fill B-side lower with 1 psi Ar Hybrid DISABLED (PG1) leave B-side upper as is Hybrid DISABLED (PG2) fill B-main (C-side) with 40 psi D2 Hybrid enabled (PG3) fill J-bot with 40psi D2 Hybrid DISABLED (PG5) leave NINJA as is DISABLED Enable gatevalves and shutters: Z-bolo Torvac gatevalve toggle (yes/no): NO Boronization(yes/no): no Overnight ECDC (yes/no): YES *and bake* ICRF(yes/no): NO LH(yes/no): no DNB(yes/no): NO Cryopump (yes/no): no Vessel temperature: 35/35/35 ------------------------------ ECDC Parameters (if requested) ------------------------------ gas and pressure: D2 at 2e-4 Torr sweep: 44/45/103 cm scan: 20/120 s Physop plan for plasma operation: ---------------------------------- Prior to first attempt, complete implementation of modifications to account for deceased flux loops f23 and f25: 1) Install new ian_007 tree in /usr/local/cmod/codes/pcs/ian/ and new version of ianup.pro in /usr/local/cmod/codes/pcs/user_algs/contihh/ 2) Turn off input_18 and input_20 (f23 and f25) in top.config.inputs and input_018 and input_020 in top.dpcs_config.inputs. Also, update the contents of four BP loop inputs that Bob will have changed: inputs #41,43,47,54 which correspond to BP12,14,18,25. 3) Change analysis::recon_vac:static_shot from 2003 to 2015 4) Modify the coefficients in analysis::top:fluxihh using /usr/local/cmod/codes/mhd/fluxihh/load_predictors_procedure.sh 5) change the weights of efit_efitin:fwtsi[[22:24]] to 0. in the analysis_model and efit_model trees. 6) Insert a bogus synthetic expression in magnetics::mag_fluxes:flux_22 and flux_24 so that MFLUX and the vacbrbz routines won't choke (and may even give decent approximations). 7) If possible, arrange for Ian to copy the new versions of ianup.pro and ian_007.* to his directories, so that mflux and mfil might work. Start with Seg 1 and 2 from 1080523011, as successful ohmic 750ka, 7e19 shot from the last day of operation. Recalculate all magnetics predictors in all segments (or just 1 and 2 and zero out 3 and 4). Tweak fields and gas as well as I can, and hope for something other than duds to tune to. Last time (1071127-29) we went for long stretches with no plasma, but at least we had fizzles. We also had more loop failures, all fixed by zapping. *************************************************************************** |
| Entered: Jun 21 2009 06:21:53:520PM |
| Author: Steve Wolfe |
| Physop plan and engineering setup for Monday 6/22/2009
If the TF scanner is available we will complete power testing with TF tests and proceed to attempt to get plasma. If not, we will start the first part of MP#555 PF Error Field Evaluation and Compensation, which calls for long single supply PF pulses under DPCS control. Note that depending on results, it may be necessary to modify the EF3 and EF4 bus connections to pulse the upper and lower coils independently, as was done on 1030717. It would also be necessary to change the A-coil taps; see detailed physop run plan below. PO: wolfe Run begins at 09:00 and ends at 17:00 ----------------- ************************************************************************* Engineering Setup for Option #2: MP#555 PF error field evaluation) ----------------- Power systems as on: 1030717007 (OH1 only, EF3 Aux power OFF) Fizzle detector on at 2.2sec, off at 2.3 sec for all shots Acoil: +Btop -Bbot -Gtop +Gbot (Non-standard) Hybrid Enabled (OFF for 1st shot) (This could be changed anytime before step 13 of the run plan, if we're not sure which experiment will be done first thing in the morning) Gas setup: Fill B-Top with 6 psi D2 Hybrid enabled (PG4) fill B-side lower with 1 psi Ar Hybrid DISABLED (PG1) leave B-side upper as is Hybrid DISABLED (PG2) fill B-main (C-side) with 40 psi D2 Hybrid enabled (PG3) fill J-bot with 40psi D2 Hybrid DISABLED (PG5) leave NINJA as is DISABLED Enable gatevalves and shutters: None unless requested Torvac gatevalve toggle (yes/no): NO Boronization(yes/no): no Overnight ECDC (yes/no): YES *and bake* ICRF(yes/no): NO LH(yes/no): no DNB(yes/no): NO Cryopump (yes/no): no Vessel temperature: 35/35/35 ------------------------------ ECDC Parameters (if requested) ------------------------------ gas and pressure: D2 at 2e-4 Torr sweep: 44/45/103 cm scan: 20/120 s Physop plan MP#555 ---------------------------------- 1) Load (or copy traces) from 1030717007 (OH1 2sec pulse at +20kA) 2) Load (or copy traces) from 1030717010 (OH1 swing -20 to +20) 3) "" 1030717008 (OH2U +20kA, 2sec flattop) 4) "" 1030717009 (OH2L +20kA, 2sec flattop) 5) "" 1030717011 (EF1U +5kA, 2 sec flattop) 6) "" 1030717012 (EF1L +5kA, 2 sec flattop) 7) "" 1030717013 (EF2U -4kA, 2 sec flattop) 8) "" 1030717014 (EF2L -4kA, 2sec flattop) 9) "" 1030717005 (EF4U/L +4kA, 2 sec flattop) 10) "" 1030717006 (EF3U/L +10kA, 2sec flattop) EF3 ON 11) If results from 9 and/or 10 are sufficiently different from the corresponding shots 1030717005 and 6, then it will be necessary to break down the bus and take pulses with the coils individually. Otherwise proceed to #13. Note that the disconnected coil should be terminated in a large resistor (or left open?) to avoid induced currents; check engineering records for 1030717001-004 to see what was done. Also, the notes indicate that it is necessary to fool the I2t circuit to allow these shots to be taken. 11A) 2 sec EF4U pulse, +4kA like 1030717001 (note IC_EF4 observer must be changed) (EF3 aux power OFF again) 11B) If necessary, 2 sec EF3U +10kA pulse like 1030717002 but with modified waveform for gentler rampdown. 12) For next shot, again reconfigure bus for Lower coil(s) only 12A) 2 sec EF4L pulse, +4kA like 1030717003 (note predictor change) EF3 AUX power OFF 12B) If necessary, 2 sec EF3L +10kA pulse like 1030717004 13) A-coil only pulse [+Btop -Bbot -Gtop +Gbot] program 4kA 14) Reconfigure A-coil to [+Btop +Bbot -Gtop -Gbot], program 4kA 15) If cases 10 and 11 were run, reconfigure the bus for normal operation and repeat shots 8 and 9 to confirm connection. *************************************************************************** |
| Session Leader Summaries |
| Physics Operator Summaries |
| Entered: Jun 22 2009 07:03:46:773PM |
| Author: Steve Wolfe |
Physop summary for Monday, 6/22/2009 This was a difficult day, but some progress was made. We took Option#1, aiming for a plasma shot after completion of TF testing. We completed the TF tests, but found another problem that prevented a successful plasma on the one attempt we made. We plan to continue this line tomorrow, after a hardware repair (see below). The day began with a series of test (no-power) shots to test the TF scanner. Eventually the bugs were worked out and the scanner software became functional. It was then discovered that some of the taps were plugged into the wrong place, resulting in bad values from the scan. This was remedied by swapping plugs, and the TF turn resistances were determined to be quite good. Once the scanner was working properly, we had to wait for the alternator to get up to speed; they had some difficulty which delayed the spin up this morning. Shots#8-14 were TF tests under PLC control. After the first one of these, we discovered that the polarity of the new \BTOR signal is reversed, so Bob had to change the expression in the tree. This required that I recalculate all the magnetics predictors (at least the ones that include the bp_coils, which need BTOR pickup correction) again before we tried out first plasma attempt on shot#15. During the course of the tf tests, the engineers also discovered a bad camac channel reading the tf supply voltage, and moved this signal to a different input. Shot#15 was a full plasma attempt based on the prepared model 1090622000, with the magnetics predictors re-recalculated to account for the change in btor sign. The result was a dud due to excessive BR_0 (over 70mT), with the BR_0 feedback driving the OH2's in opposite directions, taking OH2U to its current rail. At first I thought that the predictor was somehow screwed up, since the sign of the feedback error was backward from the actual Br0 value, as indicated both by vacbrbz and recon_vac signals. After an hour and a half of head scratching and software tests, I decided there might be something wrong with the dpcs input signals. To investigate this further we took a PLC controlled test shot (#16 a 10Ka oh commutation, like 1090619025, but without the EF4), so I could see a case with more or less balanced Br_0. Again the feedback signal on BR_0 was large and not consistent. Finally I found that the dpcs input_009 signal (F10) was about half the amplitude it should have been based on the F10 signal from the magnetics. It turns out that the iso-amp channel appears to be bad, probably the gain of 2 output amplifier. Shot #17 was a repeat on which I verified that the problem was not in the dpcs digitizer by teeing off the input_001:016 to the high channels of diag_hw:dt196_1. We then tried (#18) to workaround this problem by swapping the F10 signal over to dpcs input_028, which was previously labeled f28 (no longer exists) but had actually been connected to a diamagnetic comp loop, which had also been removed from the machine last year. I changed the hybrid config inputs to reflect this change, but missed some nodes that also needed to be changed, so when I tried to recalculate the BR_0 predictor to use this it still didn't work correctly, although the signal on input_028 looked correct. After the run we determined that Willy Burke could probably repair the bad iso-amp board in the morning, so I have restored the hybrid config in the tree to its former state (F10 on input_09 turned ON, and f28 on input_28 turned OFF, with appropriate values in the QUANTITY and STRUCTURE sub-nodes. Bob still needs to reconnect the cables to correspond to this. He should just leave input_28 with no input. The iso-amp chassis has had its fans unplugged and DC power cable removed, and the cover loosened, in preparation for the repair. The correct circuit card has been identified, we think. I have also reloaded the PCS model from shot#15, which should work once the repairs have been made. I recommend another PLC controlled test shot to confirm the feedback signal, followed by plasma attempts. |
| Session Leader Comments |
| Physics Operator Comments | |||
| Jun 22 2009 07:18:25:380AM | Steve Wolfe | Bring up PCS (the real one) Get the config warning, as expected. The model file is the power test case from Friday. Start to update the predictors, but I must have clicked something funny It's not doing the apply on wire 3. Something about linking the waveforms? Worked that time, maybe I hit apply before it finished the call. Continue. OK, do the load. Load at 22-Jun-2009 07:15:20.00 Open tree /home/wolfe/pcs_scratch -1 Open tree done Ready for shot#1, which should be a no-power test of the scanner (and everything else) | |
| Jun 22 2009 08:14:54:463AM | Steve Wolfe | Finally getting around to looking at the PCS for 1030717007 which is the model for the first shot of the MP#555 experiment. Of course, tere is no dpcs tree for this one, which is ok. It uses only seg1, which is also fine. I'm looking at it in a pcs,/safe in a separate scratch directory. Probably the best thing to do is to zero out the wires 4-6 which have plasma predictors on them, and then do imports and cut&paste for the waveforms on the different shots. Zero wires 4-6, 16. Build segment in segment 1. Zero segs 2-4 Build All save as 1090622999 in alcdata-test::/cmod/trees/test/pcs and dpcs/ about to ask alcdata-test to copy /home/wolfe/tmp.nGPfI25054/pcs_model to /cmod/trees/test/pcs/pcs_1090622999 about to ask alcdata-test to copy /home/wolfe/tmp.nGPfI25054/dpcs_model to /cmod/trees/test/dpcs/dpcs_1090622999 Open tree /home/wolfe/tmp.nGPfI25054 -1 Open tree done Now this should be ready for use if/when I need it Condirm that the copy ran on alcdata-test and quit the second PCS | |
| Jun 22 2009 07:40:02:137AM | 1090622001 | Steve Wolfe | Shot#1: No power cycle to test scanner Cycle went through Data coming in, bit noise everywhere. Looks like scanner is not working yet. |
| Jun 22 2009 07:45:20:857AM | 1090622002 | Steve Wolfe | Shot#2: Another no power cycle to test scanner Cycle went through Data coming in, bit noise everywhere. Logbook updates and banner seem to be broken on cmodwsd50 again. Still no scanner |
| Jun 22 2009 07:55:25:410AM | 1090622003 | Steve Wolfe | Shot#3: Another no power cycle to test scanner Cycle went through Data coming in, bit noise everywhere. Logbook updates and banner seem to be broken on cmodwsd50 again. Still no scanner |
| Jun 22 2009 08:18:14:840AM | 1090622004 | Steve Wolfe | Shot#4: Another no power cycle to test scanner Still no scanner |
| Jun 22 2009 08:32:38:220AM | 1090622005 | Steve Wolfe | Shot#5: Another no power cycle to test scanner Getting some scanner data now. However, it looks bad. Progress though, at least there is something there now. |
| Jun 22 2009 09:08:07:187AM | 1090622006 | Steve Wolfe | Shot#6: Another no power cycle to test scanner getting scanner data, still looks like groups of high readings. It looks like these may be the same values getting stored over again. |
| Jun 22 2009 09:35:08:710AM | 1090622007 | Steve Wolfe | Shot#7: Another no power cycle to test scanner After a cell access to swap some plugs. There seems to be some doubt as to whether the previous data are duplicated or not. This time the data look good (or at least better). |
| Jun 22 2009 09:38:44:463AM | 1090622007 | Steve Wolfe | We may be ready on the scanner. Now waiting for the alternator to come up to speed; they got off to a slow start this morning. |
| Jun 22 2009 10:29:51:233AM | 1090622008 | Steve Wolfe | Shot#8: 25kA TF test PLC control Ratiomatic is now connected, so we'll do gas on B-top and B-main. Programming is like last Friday. Got TF current, but the bus_lv signal is oscillating 200A Bob is measuring +0.8Tesla; the new loop may have the wrong polarity! Easy to fix in the tree for \Btor, but will dpcs work? The sign at the input dpcs is indeed positive, and it used to be negative. Bob needs to change the definition of \Btor in the magnetics tree. |
| Jun 22 2009 10:45:57:570AM | 1090622008 | Steve Wolfe | After shot#8, Bob changed the definition of \BTOR in the tree to account for the new minus sign. I need to recalculate all the mag predictors again to pick this up. I've verified that the get_p2v routine picks up the new value. Also, F22 is now reading zero, Bob is going to go zap it. |
| Jun 22 2009 11:09:51:390AM | 1090622009 | Steve Wolfe | Re-Call wires 1-4 in seg1 (only ones using bp-coils) to pick up the changed sign on btor. Load at 22-Jun-2009 10:49:09.00 Open tree /home/wolfe/pcs_scratch -1 Open tree done Irby found a disconnected cable to his cPCI digitizer, should work next time. Bob zapped f22, it was nearly open, now back to normal. Shot#9: 50kA TF test PLC control Got tf rog signal. btor signal looks normal, now. I'm not getting demand on pg3; that's because the fizzle is at 0.08sec and the programmed pulse starts at 0.38. Btop is working F22 is fixed but now f14 is dead. Bob back in to zap that. |
| Jun 22 2009 11:36:24:570AM | 1090622010 | Steve Wolfe | ShoT#10: Add a pg3 puff at -.14sec Load at 22-Jun-2009 11:15:55.00 Open tree /home/wolfe/pcs_scratch -1 100kA TF PLC control Got 100kA pulse, \btor is working No pressure rise from pg3 puff. Need to make it harder and longer |
| Jun 22 2009 11:40:32:760AM | 1090622010 | Steve Wolfe | Shot#11: Stretch the pg3 pulse out and raise to 100V Shorten pg4 down to 20msec as on normal shot |
| Jun 22 2009 11:55:32:047AM | 1090622011 | Steve Wolfe | Shot#11: Stretch the pg3 pulse out and raise to 100V Shorten pg4 down to 20msec as on normal shot Another 100kA TF test Ran ok, but the engineers are worried about something Got some gas maybe from B-main. Next shot I'll turn btop off to be sure. |
| Jun 22 2009 12:34:37:063PM | 1090622012 | Steve Wolfe | Shot#12: Turn the pg4 waveform off, leave 100V pg3 puff from -.594 to 0. Load at 22-Jun-2009 11:56:39.00 Open tree /home/wolfe/pcs_scratch -1 Open tree done 150kA TF pulse under PLC control. Problem in INIT, do a no-power (but should get gas) Got gas starting at -.4sec or so, rising to over 1mTorr. PG3 is working now. Next shot make it narrower pulse |
| Jun 22 2009 01:28:51:257PM | 1090622013 | Steve Wolfe | Shot#14: Next shot will be the plasma attempt. I need to recalculate all the predictors because of the BTOR sign change. First, blow away the scond PCS and do it in the live one I really need to be careful with these, because I can't tell if I miss one by anything that displays in PCS. Load from 1090622000 recalc all four segments. Build all - no warnings Change title of seg2 to "2009 0.75MA, SNL" Load Load at 22-Jun-2009 13:03:35.00 Open tree /home/wolfe/pcs_scratch -1 Open tree done Actually, Bill wants to do another PLC TF test, so they're going to disable the other supplies. This will be 165kA PLC control Got 160kA or so, Compare the \top.LOADABLES.BIT_A:MATRICES from 1090622000 and 1090622014 to verify the change of signs in btor. There are 34 differences and they all look like the signs. I think it worked. All the differences are for input_57, which is BTOR. |
| Jun 22 2009 01:32:06:833PM | 1090622015 | Steve Wolfe | Shot#15: Next shot will be the plasma attempt. Still no halpha or CIII, but Zmeter is being digitized. No current, no light - DUD. Horible BR_0, over 70mT! OH2's are very imbalanced, some problem in BR_0 |
| Jun 22 2009 03:08:15:917PM | 1090622015 | Steve Wolfe | Shot#15: Something is screwed up in the feedback. It almost looks like the sign of Br_0 is backward? Yes, this predictor is backward somehow. The sign was correct on my test shot 1090621201, at least it matched the signals from 1080523011 Run another test shot 1090622201, using data from 1090622015. It does what it did, and it looks like the sign is backward. Now try another test 202 using 1090621201 as the model; this should get the predictor I tested yesterday. Accidentally made 1090522202 instead of 1090622202, but it did the same thing. Somehow, it now thinks the br is negative when it's really positive. All of the signs look correct, down to the contents of the dpcs loadable \HYBRID::TOP.DPCS.LOADABLES.BIT_A:MATRICES which have the reverse sign of the predictor, which has the reverse sign of the physics predictor because the p_to_v is negative. It all checks out. I'm going to re-run the commutation test from Friday 1090619025 to see if there is something funny in the signals, and see what the br_0 signal does without feedbck |
| Jun 22 2009 03:24:13:003PM | 1090622015 | Steve Wolfe | Shot#15: It isn't just a sign problem. The phys_aout also has different magnitude. It looks like there may be a problem with the inputs. The phys_aout is seeing about -.02T, while the BR_0 in recon_vac is around +.07T |
| Jun 22 2009 04:07:29:630PM | 1090622016 | Steve Wolfe | Shot#16: 10KA OH comm test with PLC control And we got some ef3 induced. And the phys_aout signal for Br_0 is completely weird. For that matter, so is the Br_0.from recon_vac. Recon_vac is giving near 0, maybe -.001. vacbrbz is giving -.005, but that must be because of the bogus flux loop signals in \mag_fluxes. However, the br_0 feedback signal is .015 (phys_aout is positive which means the predictor of br_0 is negative). I still believe that the predictor is the same as being used by recon_vac, so this means there may be a problem with the inputs. F10 input to dpcs is ~.2V, but the flux_full signal is .3Wb, which should give .6V ! This could be the digitizer or more likely the iso-amp! |
| Jun 22 2009 04:30:12:933PM | 1090622017 | Steve Wolfe | Shot#17: Repeat 10KA OH comm test with PLC control Connect a ribbon cable from input1-16 to the second output patch panel, going to inputs 49-64 on diag_hw:dt196_1 The signal on input_57 of diag_hw:dt196_1 agrees with input_009 with a signal level of about 0.2V, which is wrong. This means that the output of the iso-amp must be bad. Next shot Bob will move the f10 input from input_009 to input_028, which is no longer used for the non-existent loop f28; it has something else on it. If this works, we can change the hybrid config inputs to use this input as f10. Would require recalculation, again, but it should work. Of course, if we move it back we need to recalculate again. Depends on how long it takes to get the iso-amp fixed. Also, need to consider calibration of the iso=amps; those numbers are in p_to_v_expr:gain for each input, so it should be ok. |
| Jun 22 2009 04:52:30:037PM | 1090622018 | Steve Wolfe | Shot#18: Bob is swapping the F10 signal to input_028. I will turn off input_009 and turn on input_028, change the name of input_028 to "F10" and the one on input_009 to F10BAD, and recalculate the BR_0 predictor. If it works, can do the rest of them Load it, gives a warning on the off diag test? It seems to think f10 is turned off, but it isn't. Forgot to toggle the dpcs_config inputs Do that and reload. Now it complains on all the others that used f10 before, but it's about f10bad. OK for a test Load at 22-Jun-2009 16:40:05.00 Open tree /home/wolfe/pcs_scratch -1 This should actually work as far as BR_0 is concerned. Turns out input_028 was some tf diamagnetic compensation loop, and Bob swapped that onto input_09, but it won't hurt since it's off. Signal is coming through ok on input_028, looks like the right magnitude, but br_0 signal in phys_aout is still garbage. Gives .04T error. Maybe it didn't actually load it the new predictor. |
| Jun 22 2009 05:03:16:087PM | 1090622018 | Steve Wolfe | Shot#19: Try calculating all the predictors and reloading. However, I get an error in filament on the call: % FILAMENT: Error -- can't match pflx names % Array subscript for CMAT must have same size as source expression. Open tree /home/wolfe/pcs_scratch -1 Open tree done And then it pops up a complaint that the predictor has all zero weights. It must be due to the name. I'll try changing the name and structure to what it really is, which is DCL2_HJ, a diamagnetic compensation loop that has now been cut out of the machine. Probably the filament routine is getting into trouble trying to find out the parameters for f10bad in the magnetics tree. It's funny that it filled in values before it decided to crash. Never mind, can't get it fixed before 17:00, so don't bother to take shot 19. Will work on this to get ready for tomorrow. |
| Jun 22 2009 06:02:44:640PM | 1090622018 | Steve Wolfe | Back to the hybrid::top.config.inputs For input_09 change name to "DCL2_HJ", Quantity to "DIAMAG" and STRUCTURE to "MAG_DIAM" Doesn't matter since it won't find a get_p_to_v routine for this structure, and doesn't need to. For input_028 change QUANTITY from "FLUX_PARTIAL" to "FLUX_FULL" and STRUCTURE from "MAG_FLUX_PARTIAL" to "MAG_FLUX_FULL" However, Willy has schematics for the iso-amps, and we've looked into the chassis and decided that this ought to be fixable. He has also found the isolation board test circuit. Therefore, it has been decided to try to repair the iso-amp in the morning and put things back the way they were. I'm going to undo the changes I just made to the tree. If I do that, we should be able to reload the tree from shot 1090622015 and proceed from there, once Bob has reconnected the cables to input_09 and input_28 (don't really need to put 28 back, since it's not connected to anything.) |
| Jun 22 2009 06:22:06:807PM | 1090622018 | Steve Wolfe | Back to the hybrid::top.config.inputs again. Note that if I really want to re-use the tree from shot 15 without recalculating, I need to put the input_28 stuff back the way it was, not just blank it or call it dcl2_hj. \top.config.inputs:Input_09: name from DCL2_HJ to "F10" QUANTITY from "DIAMAG" to "FLUX_FULL" STRUCTURE from "MAG_DIAM" to "MAG_FLUX_FULL" Turn it ON \top.config.inputs:input_28: name from F10 to "F28" QUANTITY from "FLUX_FULL" to "FLUX_PARTIAL" STRUCTURE from "MAG_FLUX_FULL" to "MAG_FLUX_PARTIAL" Turn it OFF \top.dpcs_config.inputs:input_009: turn it ON \top.dpcs_config.inputs:input_028: turn it OFF Now load from 1090622015 Do a build_all to see if anything squawks (it shouldn't) EditWire Br_0 and examine the inputs/weights; all ok. Do a call just to check. No complaints. ok it Now do the same for zcur2, be sure it doesn't complain; it doesn't. Load this into the live model Load at 22-Jun-2009 18:19:45.00 Open tree /home/wolfe/pcs_scratch -1 Open tree done OK, we're back where we were as far as the tree is concerned. If Willy can fix the iso-amp and Bob swaps back the cables to input_09 this should work. Recommend doing another OH comm test just to check before we turn on feedback. |
| Engineering Operator Comments | ||||
| Shot | Time | Type | Status | Comment |
| 1 | 07:26:02:273AM | Test | Bad | Tscanner test |
| 2 | 07:37:30:917AM | Test | Bad | Scanner test |
| 3 | 07:45:35:403AM | Test | Bad | scanner test |
| 4 | 08:06:23:943AM | Test | Bad | TF scanner |
| 5 | 08:25:22:140AM | Test | Bad | TF scanner highreadings |
| 6 | 08:36:51:253AM | Test | Bad | Scanner running high temps |
| 7 | 09:30:39:350AM | Test | Ok | Scanner working |
| 8 | 10:17:22:947AM | Test | Bad | TF instrumentation rack faults |
| 9 | 10:56:14:837AM | Test | Ok | TF 50KA |
| 10 | 11:32:18:743AM | Test | Ok | TF 100 KA test |
| 11 | 11:47:17:933AM | Test | Ok | 100 KA TF |
| 12 | 12:28:50:467PM | Test | Bad | Igor stuck no power |
| 13 | 12:41:18:580PM | Test | Ok | 150 KA TF test |
| 14 | 01:12:00:700PM | Test | Ok | 165 KA test |
| 15 | 01:27:06:160PM | Plasma | Ok | |
| 16 | 03:22:52:410PM | Test | Ok | OH commutation test |
| 17 | 04:14:54:553PM | Test | Ok | OH Commutation Test |
| 18 | 04:41:14:267PM | Test | Ok | OH Commutation Test |
| System Availability | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Jun 22 2009 06:28:10:510PM | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||