Tips and Tricks
Jump to navigation
Jump to search
Screen Function
All the scanning processes should be started in a screen function in order to be able to access from everywhere. In addition, it's very easy to kill an process when it hangs (just kill the screen).
- screen -S myscreen : create a new screen - screen -r : reattach to the screen - screen -x : additionally attach to the screen - inside the screen in order to deattach: Ctrl A D - inside the screen to close: exit
Avoid Odyssey Crashes
Start process with a remote desktop and when it's running, close the remote desktop.
rdesktop -g 1272x930 -k de-ch -u scanner lheppc9
NFS disks
To access to a directory through NFS.
Example : You want to have access to /terabig from lheppc46 on lheppc56 In this case lheppc46 is the server and lheppc56 is the client
Server configuration : - As superuser open /etc/exports - Add /terabig lheppc56(rw,all_squash,anonuid=1000,anongid=100,sync) ( more details on [[1]] in french :-) ) Remark : UID of scanner is 1000 & GUID of users is 100 - Do exportfs -ra to take into account your modifications - Start the NFS server : /etc/init.d/nfsserver start - If all is fine go to Client configuration , if not I'm sorry for you
Client configuration : - As superuser mkdir /terabig_lheppc46 - Open /etc/fstab ( TAKE CARE of this file !!!! ) - Add lheppc46:/terabig /terabig_lheppc46 nfs rw,hard,intr,timeo=10 0 0 ( more details on [[2]] ) - Start NFS client : /etc/init.d/nfs start - Now you should see the lheppc46's data on /terabig_lheppc46 , if not I'm sorry for you
Mount lhepsun6 & lhepsun15 -> WORK IN PROGRESS
SAMBA :
As superuser do :
mount -t smbfs //lhepsun6/share /terabig/scan/lhepsun6
For the moment no rw permissions, I have to check why
Same problem with
mount -t cifs //lhepsun6/share /terabig/scan/lhepsun6
And next line in /etc/fstab doesn't work
//130.92.139.16/share /terabig/scan/lhepsun6 smbfs rw,user,username=user,password=pass 0 0
Remark : The asked password is the password login for the user scanner
Scanning efficiency issues
Dear Francesco, this happens when you hit the tracking timeout. In this case, ZERO tracks are generated. Try increasing the timeout in SmartTracker8.xxx Cheers Cristiano ----- Original Message ----- From: "Francesco Di Capua" <fdicapua@mail.cern.ch> To: <opera-scanonline@cern.ch> Sent: Friday, July 18, 2008 10:38 AM Subject: sysal with high fog > > Dear All, > we received a brick (n.117472) related to the CC event 22877818 with very > high level of fog, > we located and reconstructed vertex in intercalibration areas (see > picture), > in order to have a reasonable scanning speed the intercalibration areas > was done with high treshold (900,840) and slope tolerance to 0.4 rad. > Quality of data is not very good, low efficiency and a lot of views with > few tracks found (see surface plot). > Trying to do a better quality volume for vertex analysis, we tried to > decrease tresholds and increase slope tolerance to 0.6, but we found a > strange behaviour of Sysal, the scanning seem to start but not microtracks > at all are found during data taking. > Do you have any suggestion for parameters to be used in this difficult > conditions? > > Thanks > Francesco > >