The bluice session Must Be "Active" not "Passive" to control the bluice window. If you don't see "User: Active", in the bottom middle of the bluice window, click-on "User: Passive" button, to toggle to the "Active" state. Typing "go" WILL open a Pop-Up window for you to enter a "nickname", But only IF user=mcfuser THIS WINDOW MAY BE BEHIND SOME OTHER ACTIVE WINDOW, IT MUST BE FOUND and dealt with BEFORE a bluice will start! This "nickname" is only used within bluice to identify who started that particular bluice session. Support Staff, or others, can open bluice on other machines, or remotely. Having a (unique) nickname for each session allows anyone running another session to see who is on AND who is ACTIVE ALSO usefule if communicating with others in User Tab CHAT Window When first starting up, if you haven't typed finish, then If there are old runs in the Collect Tab, click on (goto to) the last run number, press "reset" then "delete" it, and work your way up until you have reset & deleted run 1. OR: Click on **Staff Tab> Users> Change-Over Assistant> "Delete All Run Definitions Between User Groups adxv can be started by pressing "Open With" in the lower left corner below the image in Collect Tab select ADXV Directories must be entered by hand some scripts don't return a command prompt ######################################################## ######################################################## ######################################################## THE Following Information is NOT FOR USERS: delete /home/mcfuser/.bluice/session to start a new session ##bluice runs on dataserver3 ssh -Y blctl@dataserver3 ## the scripts which start and stop the dhs's are here: /usr/local/dcs/batchbuild/ ## those scripts start and stop the DHS .tcl programs which are here: /usr/local/dcs/bl831-dhs-tcl/ ##nuke here: vncviewer dataserver3:1 find start/stop dcss terminal/tab ./restart_dcs ## camserver and dataserver dhs each have their own terminal tab IF images appear to have NO Counts, --->>> Take Screen Shots of camserver terminal and of detector_dhs terminal!!! NO info is logged! First try this:--> in camserver terminal type "setenergy 11111", assuming that's the energy should recalibrate the energy and read in files, etc. (?) 2nd try this:--> IF still having trouble, look for "ERROR"s in dataserver dhs output (take a screen shot!!), then restart detector_dhs 3rd try this:--> (take a screen shot!!) Kill detector dhs, then stop and start camserver, then start detector_dhs ## The dhs Logs are here: /data/log/BL-831/ (on homeserver2) ######################################################## ## to startup pilatus for the first time:, Two of the labeled terminal TABS "camserver" and "detector DHS" on the screen of "vncviewer dataserver3:1.0" should already have been ssh'ed to det@pilatus in "camserver" Terminal Tab run: "camserver" in "detector DHS" Terminal Tab run: /usr/local/dcs/dhs-tcl/main/scripts/dhs.tcl BL-831 pilatus pilatus pw: Pilatus2 ######################################################### recover from dataserver3 reboot partial BFTD procedure: ssh blctl@dataserver3 cd /usr/local/dcs/dcss/linux64/ ./dcss BL-831 -s # enter the blctl password: vncviewer dataserver3:1.0 # make at least 3 tabs in a gnome terminal window # tab1: cd /usr/local/dcs/batchbuild ./start_dcs # tab2 ssh det@pilatus # Pilatus2 camserver # tab3 ssh det@pilatus /usr/local/dcs/dhs-tcl/main/scripts/dhs.tcl BL-831 pilatus ######################################################### Memhog examples.. ssh root@pilatus tcsh killall camserver killall getline mount dataserver4:/data /data tar cvf - /data/mcfuser/ | dd of=/dev/null & sleep 300 while ( `free -h | awk '/^Mem:/{print ($4+0>50)}'` ) free -h sleep 10 end # now login to vncviewer dataserver3:1.0 # re-start camserver # give camserver time to finish starting up sleep 70 killall tar umount /data