I'm learning this big messy code for accelerator modeling.
The input is a file that describes the magnets, and the code tracks particles through the accelerator and computes resulting useful stuff about the orbits and global quantities.
To access the individual magnets when writing programs, one refers first to the "family number" of the magnet, and then to the "kid number" to specify the specific magnet in the ring.
I'm always worried about what the metaphors I take in do to me. Did the person who decided on this metaphor do it out of joking? or longing? Did he really think of the storage ring he was designing as a surrogate family?
What am I getting myself into here?
2 comments:
interesting post.
there is always a question behind question.
somebody told me that during an interview. so true.
thanks nani.
insightful comment.
Post a Comment