Class and Description |
---|
xal.model.elem.ElementFactory
This class is being phased out since it requires "registration." Currently
there are no references to it and can be deleted.
|
xal.tools.beam.ParameterConverter
use
RelativisticParameterConverter |
xal.tools.beam.RmsEnvelope
Unfinished and not used anywhere
|
xal.smf.scada.ScadaCheckConnect
This class is replaced by
|
xal.model.alg.TrackerAdaptive
functionality pushed down into child class class
|
xal.tools.dyn.TranslationMatrix
Not used anywhere
|
Field and Description |
---|
xal.tools.collections.LinearBuffer.DEF_LEN_BUFFER |
Method and Description |
---|
xal.tools.beam.calc.CalculationEngine.calculatePhaseAdvance_old(PhaseMatrix, Twiss[], Twiss[])
Does not determine the phase quadrants correctly and therefore cannot produce
an accurate phase advance
|
xal.tools.beam.calc.CalculationEngine.computeTwiss(TwissProbe, PhaseMatrix, double)
This is the algorithm component for a
TwissProbe and should
not be used as the dynamics elsewhere. It has been moved to the
TwissTracker class. |
xal.smf.impl.SCLCavity.getAvgTTF(double)
Read the comments about being a hard coded kluge job.
|
xal.smf.impl.SCLCavity.getFieldWithCavityOff(double, double, double, double)
This is one of only two methods that uses stuff from outside, and
that stuff is the
sclcavity sub-package which is
completely hard coded for the SNS SCL. We must get rid of
sclcavity . |
xal.smf.impl.SCLCavity.getFieldWithCavityOff(double, double, double, double[], double)
This is one of only two methods that uses stuff from outside, and
that stuff is the
sclcavity sub-package which is
completely hard coded for the SNS SCL. We must get rid of
sclcavity . |
xal.model.probe.ParticleProbe.getFixedOrbit()
This is a duplicate of
ParticleProbe.getPhaseCoordinates() but with a
misleading name. I plan to get rid of it. |
xal.model.probe.traj.ParticleProbeState.getFixedOrbit()
This is a duplicate of
ParticleProbeState.getPhaseCoordinates() but with a
misleading name. I plan to get rid of it. |
xal.model.probe.EnvelopeProbe.getSaveTwissFlag() |
xal.model.probe.traj.EnvelopeProbeState.getSaveTwissFlag()
associated with the redundant state variable
twissParams |
xal.model.probe.EnvelopeProbe.initializeFrom(Probe<EnvelopeProbeState>)
Never used
|
xal.model.probe.Probe.initializeFrom(Probe<S>)
This method is only called from child class overrides
which are never called themselves.
|
xal.model.probe.TransferMapProbe.initializeFrom(Probe<TransferMapState>)
Never Used
|
xal.model.probe.TwissProbe.initializeFrom(Probe<TwissProbeState>)
Never used
|
xal.model.alg.Tracker.newFromEditContext(AcceleratorSeq)
I want to discourage use of this method since it return the same "default"
algorithm regardless the type of probe being used. Please refer to
. |
xal.model.alg.Tracker.newFromEditContext(String, AcceleratorSeq)
I want to discourage use of this method since it return the same "default"
algorithm regardless the type of probe being used. Please refer to
. |
xal.model.probe.Probe.performPostProcessing()
I don't think this gets used.
|
xal.tools.messaging.MessageCenter.registerSource(Object, Class<T>, boolean)
Use the version of this method that takes the synchronous type instead
|
xal.model.probe.EnvelopeProbe.setSaveTwissFlag(boolean)
If you want Twiss parameters, either take them from
the covariance matrix or use the
TwissProbe |
xal.model.probe.traj.EnvelopeProbeState.setSaveTwissFlag(boolean)
Storing only the Twiss parameters leaves an incomplete state
and may lead to erroneous results
|
xal.model.probe.EnvelopeProbe.stateResponse(String, String)
This calculation should be done using the utility class
xal.tools.beam.calc.CalculationsOnMachines
|
xal.model.probe.traj.Trajectory.statesForElement_OLD(String) |
Constructor and Description |
---|
xal.extension.wirescan.profile.ProfileData(int) |