search

crispd / issues

issues for Eric to work on ... all projects that don't have a home
2 stars 0 forks source link

Using an Optics File #15

Open crispd opened 9 years ago

crispd commented 9 years ago

The driving factor is a need for reference while tuning. If something is drastically off from what is expected, they are alerted to the fact and while tuning can verify that the difference is justified. What are the main hurdles in doing this--how much effort or time is required? Suggested goal is to display each device's 'optimal setting' in a column like RSET and address some of the functionality used in Steiner's power supply screens moving forward. This is the beginning of the discussion, once defined, specifics would be detailed in separate Issue Threads.

crispd commented 9 years ago

Out of curiosity, what do your impact lattice files look like? It might make sense if the machine's values were saved in a more useful format.. one that would also mean applicability of FRIB-required developments to ReA.

dxmaxwell commented 9 years ago

The impact lattice file is very poorly formatted, so I wouldn't recommend that, but there is a "Lattice" server that contains optics information. Maybe this is the best place to get this information.