6.30.2009
6.29.2009
Hardware Issues, but this time it's not quite as much CAEN's fault.
6.26.2009
Strange New World
----------------------------------------------------------------
Sent by Text Messaging from a mobile device.
Envoyé par messagerie texte d'un appareil mobile.
----------------------------------------------------------------
6.25.2009
----------------------------------------------------------------
Sent by Text Messaging from a mobile device.
Envoyé par messagerie texte d'un appareil mobile.
----------------------------------------------------------------
Beneath me.
--
-=//\=-
Wierdest Wikipedia crawl ever.
6.23.2009
CAEN Documentation
Writes the specified value to the specified threshold register. If
threshold_id is CVT_V792_THRESHOLD_ALL every threshold will be setted
to the same value.
Parameters:
p_data Pointer to board data
threshold_id The threshold to set. It must be a
cvt_V792_threshold_id valid id.
value The value to set : Threshold value and Kill
bit (CVT_V792_THRESHOLD_KILL_MSK) If the kill bit be isn't setted the
channel will be disabled
...
What does "If the kill bit be isn't setted the channel will be
disabled" mean? Also, how hard is it to either punctuate or not
punctuate your sentences?
6.22.2009
SUCCESS
the TDC working. It wasn't obvious, and I had to manually write some
functions that weren't very pretty, but it works. What I think it was
is that the default configuration the CAEN TDC came with was set to
look at a range outside the TDC's capabilities, so it wouldn't take
data.
This does not, however, explain why it wouldn't acquire data until I
had loaded it into LabView. My best guess is that there was something
strange configured in the TDC itself that the standard code was
struggling with, but when LabView was loaded it reset everything to a
usable state.
Now I need to loop over all the channels and export the data to files.
Not as obvious as it seems, in fact, considering once again CAEN has
half-assed their code and defined functions which do not work.
I'm ambitious this morning.
work. Friday, it miraculously decided to talk to the computer, but in
doing so, stopped taking data. I'm pretty sure the (only?) thing I've
to do now is set up some arbitrary data and then in theory add one or
two lines of code to a configuration file.
I'm quite curious as to what I'll tackle once all this CAEN stuff is done.
6.19.2009
...VME....
6.17.2009
----------------------------------------------------------------
Sent by Text Messaging from a mobile device.
Envoyé par messagerie texte d'un appareil mobile.
----------------------------------------------------------------
Symmetries
While making them, however, I did somehow manage to get the sawblade to jump off it's track on the band saw, which produced a mighty scary noise, but had no other ill effects. I'm hoping that I get to spend more time in the machine shop, albeit I don't know if my supervisor has any more work for me to do there. I can think of 1001 different <i>personal</i> projects to work on, but I don't think that David would appreciate paying me while I cut custom components for my launch pad.
Today, I test out an HV power supply and try to get the last data points required to finish my PMT calibration.
6.16.2009
6.10.2009
This could have ended badly.
Firefox and hit enter when you share an office with 5 other people.
Oh, and if you do happen to do it, try not to leave it up on your main
monitor for something on the order of 10 minutes while you work on
your netbook.
For the record I was looking for programming aide. Man, the internet
sure is something.
----------------------------------------------------------------
Sent by Text Messaging from a mobile device.
Envoyé par messagerie texte d'un appareil mobile.
----------------------------------------------------------------
6.09.2009
Machining Parts
6.05.2009
I love tech support
Until today.
I got an email from someone I've been corresponding with only to find out that I don't have the up-to-date version of the software. This isn't because I accidently downloaded the wrong version, at the time of writing this, there was only one version available for download. Now, I have V1.01 of some software I got via a special URL whereas if you're going to their website you can only get V1.00 which doesn't have all the libraries you need to get the (supposedly) supported VME cards to work. How the hell is anyone supposed to figure out that the company supplied software, which advertises its module compatibility, <i>isn't compatible</i>. Excuuuuuuse me, CAEN for not having the magic space brain (Zero Punctuation, anyone?) required to figure out that the driver installation process requires a month of back and forth emailing with various employees.
All that said, even having the updated software doesn't get the damn TDC to work.
Almost quitting time. In 15 minutes if my supervisor isn't ready he's going to release me.