Skip to content

LabWare CEC 2016 and HAL

April 25, 2016

In the past few weeks, I’d written about the fact that I’m not attending the LabWare CEC. If you’re there, right now, please don’t look for me because it won’t be a fruitful pastime. When I wrote about the fact that I won’t be attending this event, I’d mentioned the session about HAL and several people have asked me about it so I’m going to give a link for those who are curious.

The link is: 2016 LabWare CEC

Look at the first item on page 7. It’s entitled “HAL.” In one of my posts, I joked about avoiding HAL. In case you don’t know this, HAL was the computer in a space movie and meant to be Big Brother, watching and monitoring everything the crew did. Another tidbit is that the letters “HAL” are one letter away from the letters “IBM.”

However, I have no idea what this session could possibly be, especially since, even today, it says it will be added (yes, I know the conference has started and it’s still not defined but that’s just how it is). Would LIMS Administrators be coming together to figure out how to spy on their users? It seems unlikely. But only those who attend will know, if they’re willing to tell what nefarious deeds they learn at this session.  😉

Gloria Metrick
GeoMetrick Enterprises

4 Comments leave one →
  1. John Newtown permalink
    April 25, 2016 8:54 am

    High Availability LIMS- deployment techniques for high availability enterprise systems

  2. April 25, 2016 9:01 am

    Once, again, proof that we have too many acronyms in the world.

    Thanks for illuminating us, John, and have a great week at the CEC! 🙂

  3. Charles Moore permalink
    April 27, 2016 5:30 pm

    Sitting in the session now. “High availability” in LabWare speak means “background processors.” The course is covering the tools necessary to set these up, monitor them, etc.

  4. April 27, 2016 5:41 pm

    That’s a good topic because I don’t think it’s obvious regarding how to get the most of out these. I had worked on a project where there were huge volumes of data travelling between systems and the background processes were determined the best route to send that data but the volume of work was spent in writing LIMS Basic to manage all this. It worked well but it did require some unique strategies over what one does from inside the system for user-driven programs.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: