[Hps-ecal] HPS software on CLON machines

[Maurik Holtrop]

Hello Andrea,

Thank you for bringing this up, it is indeed time to start worrying about this.

Are these the "new and improved" clon machines in the Hall-B counting house?

I am asking because we will need the newer, faster, machines for our DAQ, and I don't know if those are there yet.

It would make a lot of sense to have all the DAQ machines at the same release, so we don't have different machines with different capabilities. I think we should have Java 1.7 on all our machines. If this cannot be the standard install, then indeed we should have the Java 1.7 distribution in a commonly accessible directory, that is NOT someone's home directory.

We will need to run the monitoring app on a machine that has a fast ET ring. It does not need to be the main DAQ machine (that runs the event builder), but it should be a reasonable fast machine with a fast ET connection.

I think we can run from the JAR files OK. Compiling new versions should probably proceed elsewhere. We do need to make sure that all machines use the same set of JAR files, so again we have need for a common directory.

Best,
	Maurik



On Oct 8, 2014, at 2:36 PM, Andrea Celentano <celentan at jlab.org> wrote:

> Dear all,
> during the HPS commissioning and data taking runs, we need to use the 
> HPS-software to monitor the ECAL (and probably the SVT too).
> 
> This requires to install the hps sofware on the clon machines.
> 
> There're different ways to do this, and some pre-requirements. I try to 
> list them here, to discuss with you how to proceed. I'll not do any 
> change on any configuration before we have a clear plan.
> 
> 1) Java.
> 
> HPS needs Java 1.7 (at least). I've seen that on some clon machines we 
> have java 1.7 (clonpc11, clonpc1), while on others we have java 1.6 
> (clondaq3)
> 
> I see that, to by-pass this problem, the .cshrc of the hpsrun account 
> was modified with:
> 
> setenv PATH /misc/home/rafopar/Apps/Java/jdk1.7.0_67/bin:${PATH}:
> 
> - Do we need to install java 1.7 on all clone machines? If so, I suggest 
> to have it in some "common" folder that is seen by all clones (or, at 
> least, by the machines that we expect to run the monitoring software on)
> 
> 2) HPS-Software
> 
> We can proceed in two ways:
> - Install only the compiled jar file
> - Install the source code and compile it
> 
> Probably, since we need only the monitoring application, we can proceed 
> with the first option. To proceed with the second, we need:
> -- Access to the svn repository from the clon machines 
> (svn://svn.freehep.org/hps)
> -- maven installed on the clon machines
> 
> Thanks for your feedback
> 
> Andrea
> _______________________________________________
> Hps-ecal mailing list
> Hps-ecal at jlab.org
> https://mailman.jlab.org/mailman/listinfo/hps-ecal