Skip to main content

SageMath, Where Objects Rock and Scripts Don't

I moved the Sage simulation of the can crusher to an object oriented implementation today.  A few days ago,I was worried this might have been a bit of overkill and just a subconcious desire on my part to place the project in a code format I'm used to seeing things in.  I hit an example yesterday that convinced me otherwiser, and only a few short, OK,  and somewhat grueling, hours later, I had a much easier to use OO simulator.

Prior to yesterday, my usage mode of the can crusher code was as follows:
1.  Evaluate the cell that contained the initializaiton code.  There were some declarations of global varaibles and a little bit of code that atually ran on evaluation to place values in these variables.
2.  Evaluate the cells that contained the current calculating function and the can moving function separately.
3.  Evaluate the cell that contained the simulation code.

This, as far as I knew had to be done every time I wanted to change any values and run a simulation.  I was constantly worried that I might not evaluate the cells in the correct order or that a rogue global variable might escape initialization.

The clincher came when I wondered if there was a difference between the simulated current through the driving coil when the can was allowed to crush and when it was not.  In order to do this, I had to execute the above procedure, then, copy the results of the global current array into a placeholder array, then modify the simulation code, then run the above procedure again, and finally graph the new global current array and the placeholder array on the same plot to get the following result


Contemplating the stress of wondering what I had called my placeholder variables and whether or not I'd run through the initialization procedure correctly every time led to this morning's object oriented re-write.  What I wound up with was a simulator object that encapsulates all the initialization procedures and its own set of member variables that correspond to the previous set of globally available variables  Now, to create a comparison like the one shown above, I can just create two simulations, passing both of them the same limit for the number of simulation steps to run, but tell one of them to turn the can moving portion of the code off, like so, (my simulator class is named Crusher):

nm_crushtest = Crusher()
nm_crushtest.set_movecan(False)
nm_crushtest.simulate(372)

crushtest = Crusher()
crushtest.simulate(372)

After the simulations have run, the graph is easy to generate:

nomove = list_plot(nm_crushtest.coilOutTime[0:372, 0:2], color='red')
move = list_plot(crushtest.coilOutTime[0:372, 0:2], color='blue')
show(nomove + move)


The Grueling Bit
If you're coming from a C++ background, the only part that will drive you nuts is having to put 'self.' in front of every member variable every time it is used in the class definition.  I still think I must have been doing this wrong and hope that I kind Python expert will correct my gruesomely bad coding style soon.

References:
1.  The Python object oriented documentation
https://docs.python.org/2/tutorial/classes.html

2.  Upcoming useful docs: How to handle large +Sage Mathematical Software System programs
http://www.sagemath.org/doc/tutorial/programming.html

3.  The can crusher simulator in it's many revision controlled incarnations
https://github.com/hcarter333/cancrusher

Comments

Popular posts from this blog

Cool Math Tricks: Deriving the Divergence, (Del or Nabla) into New (Cylindrical) Coordinate Systems

The following is a pretty lengthy procedure, but converting the divergence, (nabla, del) operator between coordinate systems comes up pretty often. While there are tables for converting between common coordinate systems, there seem to be fewer explanations of the procedure for deriving the conversion, so here goes!

What do we actually want?

To convert the Cartesian nabla



to the nabla for another coordinate system, say… cylindrical coordinates.



What we’ll need:

1. The Cartesian Nabla:



2. A set of equations relating the Cartesian coordinates to cylindrical coordinates:



3. A set of equations relating the Cartesian basis vectors to the basis vectors of the new coordinate system:



How to do it:

Use the chain rule for differentiation to convert the derivatives with respect to the Cartesian variables to derivatives with respect to the cylindrical variables.

The chain rule can be used to convert a differential operator in terms of one variable into a series of differential operators in terms of othe…

Lost Phone

We were incredibly lucky to have both been in university settings when our kids were born.  When No. 1 arrived, we were both still grad students.  Not long after No. 2 arrived, (about 10 days to be exact), mom-person defended her dissertation and gained the appellation prependage Dr. 

While there are lots of perks attendant to grad school, not the least of them phenomenal health insurance, that’s not the one that’s come to mind for me just now.  The one I’m most grateful for at the moment with respect to our kids was the opportunities for sheer independence.  Most days, we’d meet for lunch on the quad of whatever university we were hanging out at at the time, (physics research requires a bit of travel), to eat lunch.  During those lunches, the kids could crawl, toddle, or jog off into the distance.  There were no roads, and therefore no cars.  And, I realize now with a certain wistful bliss I had no knowledge of at the time, there were also very few people at hand that new what a baby…

Lab Book 2014_07_10 More NaI Characterization

Summary: Much more plunking around with the NaI detector and sources today.  A Pb shield was built to eliminate cosmic ray muons as well as potassium 40 radiation from the concreted building.  The spectra are much cleaner, but still don't have the count rates or distinctive peaks that are expected.
New to the experiment?  Scroll to the bottom to see background and get caught up.
Lab Book Threshold for the QVT is currently set at -1.49 volts.  Remember to divide this by 100 to get the actual threshold voltage. A new spectrum recording the lines of all three sources, Cs 137, Co 60, and Sr 90, was started at approximately 10:55. Took data for about an hour.
Started the Cs 137 only spectrum at about 11:55 AM

Here’s the no-source background from yesterday
In comparison, here’s the 3 source spectrum from this morning.

The three source spectrum shows peak structure not exhibited by the background alone. I forgot to take scope pictures of the Cs137 run. I do however, have the printout, and…