 |
Workers Section |
FallBack Scenario for Demonstration
We cover two contingencies for component failure and how we will overcome them
to still have a successful demonstration. The first probability although small
is not zero and thus we need to be ready for it to happen. The second failure is
a much lower probability.
THE DIII-D Tokamak Does Not Run
- A Linux laptop will be brought to SC03 by GA to act as MDSPlus server
- Scripts on this machine will fake the DIII-D shot cycle including the
data acquisition events.
- EFIT and TRANSP can still be launched at PPPL.
- Need to fake RT displays and shot cycle status as well.
- We can still communicate with DIII-D control room and have someone man
the AG node.
- Someone can enter a few log book entries as well.
Complete Loss of Network Connection to GA and PPPL
- Local MDSplus server as above will cover shot cycle.
- EFITs and TRANSP will not actually be run, but we will wait the
appropriate time to issue the event that states they are completed.
- Having EFIT and TRANSP run at SC03 seems to be very tough and the
probability of total network loss is small.
General Comments
- Our fallback scenario will involve real pulses stored in our MDSplus
server. This will allow us to do a demo dry run.
- This will also make a very compelling demo even if we suffer the failures above.
