search

alcap-org / AlcapDAQ

Alcap DAQ
alcap-org.github.io
8 stars 0 forks source link

Alcapana not accepting modules #273

Open dmalexan opened 9 years ago

dmalexan commented 9 years ago

One of our undergraduates is attempting to compile Alcapana to look at some of the data. While we are able to get the program to compile (with a minor edit to the location of libmysql.so to get midas to compile) and run, it does not give the full output. For some reason the only module that is included is the vacuum module.
I have tried double checking the MODULES file, the Makefile.MODULES, MODULES.h, etc. All object files are properly constructed. We've tried changing which modules are used, but always get the same result.
Checked the init calls for the modules with a simple "hello world", got nothing. Used a debugger to check for the init calls in mana and the only init request passed to it is from the vacuum module. We tried recompiling midas, compress and md5-lib along with recompiling alcapana, yet the behaviour persists. Has anyone else run into an issue like this?

AndrewEdmonds11 commented 9 years ago

Hmm.. that's an odd one. A few random questions that may, or may not, help:

  1. What operating system is this on?
  2. Are you in a subdirectory of work that is the same as $USER on your machine?
  3. Alcapana compiles fine, right?
  4. Are you just running a command or are you using =RunAlcapana.sh= or some other script to run it?
dmalexan commented 9 years ago

I'm not sure of the OS. I can say that we tried running in both the $user folder and the data_quality folder under work. Alcapana compiled fine in both cases, though I need to take a closer look at the make output. The student had initially been running the bash scripts, though we cleared the WireMap, loaded a new odb and tried running the program directly. It's possible the shell script messed with another odb setting, but I would have expected that to get cleared up with the WireMap

dmalexan commented 9 years ago

OS is Ubuntu 14.04

AndrewEdmonds11 commented 9 years ago

I have the same OS on my laptop. I've just recompiled alcapana in my $USER directory with most of the data quality modules and ran alcapana from the command line (./alcapana -i ../../../../data/raw/run03580.mid -o hist.root -T tree.root) on run 3580 (I'm on commit ac5e56b) and everything seems fine.

I don't know what else to suggest... Which commit are you running on? We can do a diff and see if something's crept in.

jrquirk commented 9 years ago

I confirm what Andy says. I am also running 14.04 and had no issue. Could you do the following

  1. Stash your changes and go to the latest version of branch R15a
  2. Remove all AlcapDAQ/analyzer/work/$USER/.*.SHM
  3. Source thisdaq.sh
  4. Load the ODB for a run whose raw data you have
  5. Use an AlcapDAQ/analyzer/work/$USER/MODULES file that produces a histogram other than the vacuum histograms
  6. make clean and make AlcapDAQ/analyzer/work/$USER/
  7. Go the the user directory and run ./alcapana -i run?????.mid -o hist.root with the run you have.
  8. Check hist.root for the histograms.

If this doesn't work, please post

  1. The branch/commit you used
  2. The run you used
  3. The MODULES file you used.
dmalexan commented 9 years ago

We had tried all those steps except the manual removal of the .shm files. At this point I recommended a wipe and clean install. Last I heard this worked, though the cause of the problem is still uncertain.