8-ID
  8-ID Beamline logbook mirror, Page 40 of 44  Not logged in ELOG logo
ID Date Author Type Category Subject
  85   Sat Jul 29 10:29:50 2006 Mark Sutton8-ID-IProblemLakeshore temp controller
The Lakeshore temperature controller gets into a state where the power output
stay 0%. This means that we can not do temperature quenches under macro control.

Suresh added:
Temporary solution:

there is a parameter called HTRST which tells the status of the heater. I have added that in the Lakeshore MEDM to check for it every time we do "te " or "temp_wait" and reset if there is an error. This should take care of the problem while setting the temperature or while waiting for equilibration. This wont work if this error occurs during the measurement. We need to come up with some other way for this.
  84   Wed Jul 26 18:04:19 2006 Mark Sutton8-ID-IProblemsamz disagreement between spec and epics
The first time we moved samz it changed position. Ie started
at samz=0 with beam, after moving samz=0 had not beam. Think
this is because spec and epics were out of sync. Since
we had done a fresh on spec and samz had not been before
this is some sort of bug. A fresh start on spec should have
resynced the motors position. By the way this would have
been trivial to fix if dial units were properly used!!!!!!!
  83   Tue Jul 25 14:47:11 2006 Michael Sprung8-ID-Beamline Hardwareburn spot on 8-ID-G Beryllium window
As we were starting to setup the experiment for Oleg we found that the front part of the flight path was not under vacuum. We found an unseated o-ring at the 3rd JJ slit just before the ion chamber. It seems highly likely that the beam path was at atmospheric pressure for the whole previous experiment, which used the 3rd harmanic. We found a burn spot on the polished Be window. The window needs to be replaced in the shutdown.
  82   Mon Jul 24 15:56:59 2006 Larry LurioBug reportSoftwareThe epics serial put command
In order to talk to the Lakeshore l370 temperature controller I need to add a sleep command

def l370_put(cmd) '{
sleep(0.5)
epics_put(LS370_PUT,sprintf("%s\n",cmd))
sleep(0.5)
}'

Note that sleeps seems to be needed both before and after the epics_put.
  81   Mon Jul 24 15:50:40 2006 Xuesong8-ID-Ispec macrosKnown problems for using cmos (and smd?) camera
Since there is no physical shutter for these cameras, and the acquistion might
be much faster than writing the file to disk, the camera will be unexpectedly
illuminated by X-ray during the time when the Image server dumps the memeory
to the disk.

Brian said that the NumExposure PV is supposed to decreased immediately to 1
(but not the file index number) as long as the series is done. So I made a
macro ccdwait_fb_cmos (in ~8idiuser/local_macros/series_params_8idi_cmos.mac)
which will block beam once spec thinks the data acquisition
is done by polling the NumExposure PV. You should redefine ccdwait_fb
to ccdwait_fb_cmos if use these two cameras.

I am not sure it protects the camera as expected. It still need to be tested.

Xuesong
  80   Mon Jul 24 15:28:57 2006 Xuesong8-ID-Ispec macrosWrite image file to local disk in case of loss connection to samba disks
I modified the

writebatchinfo
writeinfo

macros and saved them in
~8idiuser/local_macros/writebatchinfo_local.mac

There is a global flag WRITE_LOCAL, if it is set to 1, the image file will be
saved to the PC local disks and the batch info will be stored in the linux
directory which user assigned.

Here is an example to write locally in the do file

data_dir = "F:/DATA/cmos_July06/"
log_dir = "/home/8-idi-a/cmos_july06/logs"

# for writing to local dir only
global info_dir
WRITE_LOCAL = 1
info_dir = "/home/8-idi-a/cmos_july06/batchinfos/"
makedir info_dir

I know it is not convenient to keep the info files and the images files separately. But
this at least lets the experiment going if the samba mount is dead.
  79   Mon Jul 24 15:12:40 2006 Xuesong8-ID-Ispec macrosupdates on xpcs ccd control macros
I have added two more detector entries in for the cmos camera and smd camera.
The new macros are temporarily in ~8idiuser/local_macros/

beamparams_cmos.mac
series_params_8idi_cmos.mac

For cmos camera, extra series parameters are added:
tilting angle
user_gain
cmos_clock
roi width and roi offset (since brian's Image server only takes the current ROI as the full chip size. we need
know the x y offset in the beamparams and according correct the value frp, VStart HStart PV
and write them in the info file in order to calculate the q values as usual)


The current macros in site_f should be updated to use these two new detectors.
  78   Mon Jul 24 14:48:49 2006 Xuesong8-ID GeneralControlscheck an autosave file against a running ioc: an useful program to prepare IOC rebooting.
FYI, This is what Tim Mooney replied to Daniel Legnini's question:

Daniel Legnini wrote:
> stefan and i rebooted our crate a while ago, and found to our dismay
> that the positions for all our motors were lost. we have had numerous
> problems over the past few years with this problem, but it has
> (always?) been the settings, and (never?) the positions. well, this
> time the settings were OK, but all motors had to be manually "set" from
> a printout. luckily, we have learned the hard way to religiously
> follow the procedure of printing this info out at least a couple times
> a day, so it "only" took the two of us 1-1/2 hours to get 90% of our
> setup back. all this was done as the users sat and watched, instead of
> doing the scan they had set up.
>
> i am sending this to the rest of the group to alert you of the
> potential for similar problems on your own crates. i have no evidence,
> but suspect that the recent work on and rebooting of the beams server
> *might* have contributed to this.
>
> i suggest checking for proper functioning of your autosave processes,
> and making sure that the positions and settings files are not only
> being written (we have lots of files, written all day long), but are
> actually reflecting the PVs in your crate before the next reboot...
>
> --dan
>

Stefan asked for a way to check an autosave file against a running ioc,
so one could know it's going to work before rebooting. I just wrote a
program to do this. There is a copy in /home/beams/BCDA/bin/solaris, and
another copy in /APSshare/bin/solaris. The program is named asVerify, and
you run it like so:

/home/beams/BCDA/bin/solaris/asVerify auto_positions.sav

or, if you want to see all the saved and live PV values.

/home/beams/BCDA/bin/solaris/asVerify -v auto_positions.sav

Currently, asVerify doesn't check array PV's, and it's mechanism for
skipping past them in the .sav file fails harmlessly for large enough
arrays. Also, the program doesn't defend itself against the .sav file
being overwritten while it's being verified. I'll fix these things
eventually, but the tool works well enough now to be at least useful.

If asVerify detects big problems, we might be able to fix autosave in
place by removing and recreating an autosave save set. More likely,
autosave is hosed for a reason, and the best we'll be able to do is
find the best existing .sav file. Eventually, the output of asVerify
will be useable directly as an autosave restore file, in the event
autosave is trashed while channel access is still ok.

If you think of something else that might be useful, let me know.

....


The new version also can write a file that autosave can use at restore time.
Here's the command:
asVerify -r auto_settings.sav
or
asVerify -vr auto_settings.sav
if you want to see all the PVs.


Daniel G. Legnini wrote:

> On Jul 14, 2006, at 2:48 PM, Tim Mooney wrote:
>
> .
> .
> .
>
>> If you think of something else that might be useful, let me know.
>>
>> --
>
>
> i was discussing this very idea with stefan right after recovering
> from the problem the other night.
>
> what i would find most useful is if this program were to set a PV with
> it's return status, so we can easily incorporate (and automate)
> signalling people as to the health of the autosave process. i imagine
> tim's asVerify being run periodically, and/or from a medm menu button,
> and reporting back what's going on to the commonly accepted user
> interface we all use. various screens at various end stations can then
> be simply updated to incorporate this new checking of autosave
> functionality.
>
> for this first proof-of-concept work, we can take care of automatically
> running the program periodically or setting up a button somewhere to
> run it, and adding any status PVs to our primary medm screen(s) (but if
> someone else wants to do that, too, please feel free).

For now, you can do this in the shell. asVerify returns the number of PV's
whose caget values differed from the .sav-file values. csh sets the variable
'status' to the return code of the most recent command. So, if you're running
csh, the following example should work:

$ asVerify auto_positions.sav
$ caput 2xfm:userCalc10.A $status
  77   Thu Jul 20 11:46:42 2006 Alec8-ID GeneralSoftwareconvert.i script for uncompressing SMD data
From yorick, first read in convert_imm3.i and then can use following file to uncompress compressed SMD data:

parent = "/home/8-idi-a/simon_0606/"


//change the foll. 3 lines and change the format command for >9999
//images
child="lu_w_13_34.35C_01"
first_frame=1
last_frame=4000

//change the above 3 lines

first_frame=swrite(format="%04d",first_frame)
last_frame=swrite(format="%04d",last_frame)


print,oldname,newname
oldname = parent+child+"/"+child+"_"+first_frame+"-"+last_frame+".imm"
newname = parent+child+"/"+child+"_ucp_"+first_frame+"-"+last_frame+".imm"

convert_imm(oldname,newname)
  76   Wed Jul 19 09:52:57 2006 Alec8-ID GeneralControlsEPICS boot scripts
EPICS boot script location to see what serial port is assigned to what, for example ...

/home/xorApps/epics/synApps_4_5/ioc/8id/iocBoot

then go to the crate and then look at st.cmd
  75   Wed Jul 19 09:34:14 2006 Laurence Lurio8-ID-ExperimentNotes from Mulders/Burns/Chan/Lurio run
1) Does this electronic notebook get backed up?
2) Need to order for next time some High-voltage patch cables. In the mean time, we have disconnected cables GSC/GSA 1 and 2, (which were bundled together) and directly patched GSC/GSA 1 from the HV supply to the JJXRAY ion chamber.
  74   Fri Jul 14 11:09:17 2006 Laurence Lurio8-ID-IExperimentNotes from run
Speckle at 20x20 micron slit settings, for 5.3 m distance expect 45 micron speckles resolved with 7 micron pixels.

Scattering from aerogel sample


Callibration of flux v.s. attenuator settings at 40x40 micron slits 7.35 keV (corrected E)

Att Flux Attenuation
7 5.7e7 145
6 1.1e8 77
5 2.2e8 37
4 4.5e8 19
3 8.9e8 9.3
2 1.7e9 4.9
1 4.0e9 2.1
0 8.3e9
  73   Wed Jul 12 15:57:07 2006 Alec8-ID GeneralComputers and NetworkXOR server network path names
From http://ww2.xor.aps.anl.gov/computing/info/Computer_Info/200505/20050513.0.html

and in general the xor info server site
http://ww2.xor.aps.anl.gov/computing/info/Computer_Info/Computer_Info.html

Solaris Path Linux Path
------------- -----------------------------
/home/1-bm /net/beams-nfs/export/1-bm
/home/1-id /net/beams-nfs/export/1-id
/home/2-bm /net/beams-nfs/export/2-bm
/home/2-idb /net/beams-nfs/export/2-idb
/home/2-idb1 /net/beams-nfs/export/2-idb1
/home/2-idd /net/beams-nfs/export/2-idd
/home/2-ide /net/beams-nfs/export/2-ide
/home/aussie /net/beams-nfs/export/aussie
/home/beams /net/beams-nfs/export/beams
/home/beams1 /net/beams-nfs/export/beams1
/home/ftp1 /net/beams-nfs/export/ftp1
/home/joule /net/beams-nfs/export/joule
/home/local /net/beams-nfs/export/local
/home/sector3 /net/beams-nfs/export/sector3
/home/2bm-tomo /net/users-nfs/export/2bm-tomo
/home/8-id /net/users-nfs/export/8-id
/home/8-ide-a /net/users-nfs/export/8-ide-a
/home/8-ide-b /net/users-nfs/export/8-ide-b
/home/8-ide-c /net/users-nfs/export/8-ide-c
/home/8-ide-d /net/users-nfs/export/8-ide-d
/home/8-idi-a /net/users-nfs/export/8-idi-a
/home/8-idi-b /net/users-nfs/export/8-idi-b
/home/8-idi-c /net/users-nfs/export/8-idi-c
/home/8-idi-d /net/users-nfs/export/8-idi-d
/home/ftp2 /net/users-nfs/export/ftp2
/home/scratch /net/users-nfs/export/scratch
/home/sector30 /net/users-nfs/export/sector30
/home/sector4 /net/users-nfs/export/sector4
/home/users /net/users-nfs/export/users
/home/users1 /net/users-nfs/export/users1
  72   Wed Jul 12 11:18:47 2006 Larry8-ID-IComputers and NetworkOpen office doesn't work.
Open office for linux doesn't seem to be properly configured on Amber
  71   Wed Jul 5 16:58:10 2006 Alec8-ID-IExperimentNear Field Speckle
ti4 table potentiometer and motor readings before moving coolsnap camera

ti4zu - 7.2081 VDC -> 9.0786 mm

ti4zdi - 4.5267 VDC -> 14.8594 mm

ti4zdo - 4.2067 VDC -> 16.2452

And EPICS User / Dial positions
ti4xu = 14.00098 mm / 14.001115 mm
ti4xd = 16.00095 mm / 16.00095 mm
ti4zu = 6.11455 mm / 6.114415 mm
ti4zdi = 14.72946 mm / 14.72946 mm
ti4zdo = 16.659225 mm / 16.659225 mm

ti4_x = 14.621634 mm
ti4_z = 10.899796 mm

moved mono on Friday
ti1_x = 5.87
  70   Wed Jul 5 14:13:27 2006 Larry 8-ID-IExperimentNotes from polymer film expt. June 2006

Quote:
The flux at 7.35 keV with 20 x 50 micron slits is 1.09 e10

The go_pos macro for yorick has been updated to be consistant with the renumbering of the motors.
The move_motors.mac macro has been updated for the positions appropriate to the new detector positions
The bstop to detector distance was measured to be approximately 10 inches

The first frame of the ccdseries seems to have a higher intensity than all the other frames. I suspect that this is an indication that the shutter is sticking.

I found a bug in coherent. The omitsaturated.i file has been modified. See comment in the file.
Attachment 1: DSCN0896.JPG
DSCN0896.JPG
  69   Wed Jul 5 14:13:13 2006 Larry 8-ID-IExperimentNotes from polymer film expt. June 2006

Quote:
The flux at 7.35 keV with 20 x 50 micron slits is 1.09 e10

The go_pos macro for yorick has been updated to be consistant with the renumbering of the motors.
The move_motors.mac macro has been updated for the positions appropriate to the new detector positions
The bstop to detector distance was measured to be approximately 10 inches

The first frame of the ccdseries seems to have a higher intensity than all the other frames. I suspect that this is an indication that the shutter is sticking.

I found a bug in coherent. The omitsaturated.i file has been modified. See comment in the file.
Attachment 1: DSCN0893.JPG
DSCN0893.JPG
Attachment 2: DSCN0894.JPG
DSCN0894.JPG
Attachment 3: DSCN0895.JPG
DSCN0895.JPG
  68   Wed Jul 5 14:12:36 2006 Larry 8-ID-IExperimentNotes from polymer film expt. June 2006

Quote:
The flux at 7.35 keV with 20 x 50 micron slits is 1.09 e10

The go_pos macro for yorick has been updated to be consistant with the renumbering of the motors.
The move_motors.mac macro has been updated for the positions appropriate to the new detector positions
The bstop to detector distance was measured to be approximately 10 inches

The first frame of the ccdseries seems to have a higher intensity than all the other frames. I suspect that this is an indication that the shutter is sticking.

I found a bug in coherent. The omitsaturated.i file has been modified. See comment in the file.
Attachment 1: DSCN0890.JPG
DSCN0890.JPG
Attachment 2: DSCN0891.JPG
DSCN0891.JPG
Attachment 3: DSCN0892.JPG
DSCN0892.JPG
  67   Mon Jul 3 10:54:46 2006 LarrySuggestion BoxEPSPaging beamline staff for eps trips
It might be a nice idea if the EPS were set up so that it could automatically page someone when there is an eps trip.
  66   Wed Jun 28 14:40:41 2006 Larry 8-ID-IExperimentNotes from polymer film expt. June 2006
The flux at 7.35 keV with 20 x 50 micron slits is 1.09 e10

The go_pos macro for yorick has been updated to be consistant with the renumbering of the motors.
The move_motors.mac macro has been updated for the positions appropriate to the new detector positions
The bstop to detector distance was measured to be approximately 10 inches

The first frame of the ccdseries seems to have a higher intensity than all the other frames. I suspect that this is an indication that the shutter is sticking.

I found a bug in coherent. The omitsaturated.i file has been modified. See comment in the file.
ELOG V3.1.4-395e101