| ID |
Date |
Author |
Type |
Category |
Subject |
|
76
|
Wed Jul 19 09:52:57 2006 |
Alec | 8-ID General | Controls | EPICS 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 |
|
77
|
Thu Jul 20 11:46:42 2006 |
Alec | 8-ID General | Software | convert.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) |
|
78
|
Mon Jul 24 14:48:49 2006 |
Xuesong | 8-ID General | Controls | check 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 |
|
87
|
Sun Aug 6 14:53:08 2006 |
Mark Sutton | 8-ID General | EPS | D-I transport vacuum trip |
The EPS tripped on a vacuum fault for the D-I transport. Checked vacuum readings
and they were good. Reset alarm and it cleared. Called Alec to get the security
code for the EPS panel in order to open the value (downstream of D-mono). Opened
valve and came back on line with no other problems. Time approx 2:00PM Sunday Aug 6. |
|
89
|
Tue Aug 8 01:34:57 2006 |
Mark Sutton | 8-ID General | Software | Notes on new version and setup for yorick |
I added the new Yorick (2.1) to the tree in yoradmin.
I got the source from the Sourceforge site and put it in ~yoradmin/src/. After untarring the files I did a
make relocatable to create a tgz file with the executables and I installed this in
the yoradmin home directory. To make the executable available, a symbolic (not a hard)
link pointing to this file should be installed. I added such a link in ~idguser/bin/yorick2.1
as an example. This allows idguser to run yorick for the old version and yorick2.1 for the
new one. Other users can do this or a link can be put in /usr/local/bin.
Since contrib should be in the same directory as
i/ and i0/ I added a symbolic link pointing to ~yoradmin/Yorick in this directory.
I added the file resetpath.i in the i-start directory. This allows a custom.i in
the current directory to override the one in ~/Yorick.
Since the new yorick has plugins, I added a plugins directory to the path at the same
level as plot/ fit/ etc. The way I use this directory is to put the source in a subdirectory
and create a hard link to the .i file and the .so file. See droplet/ droplet.i and droplet.so.
If done correctly #include "plugins/droplet.i" should work. Note it is also required that
a plug_dir "/home/users/YORADMIN/Yorick/plugins" command be executed first. I put this in
my custom.i file.
The img and epics_yor should be converted to plugins at some point.
Have fun,
Mark |
|
90
|
Tue Aug 8 01:37:29 2006 |
Mark Sutton | 8-ID General | Controls | Too easy to close wrong shutter |
The open/close shutter buttons on the epics beamline windows are too small
and too close together. I would recommend that each only have its own shutter
bottom, a G user will not accidentally close the I shutter, etc. |
|
92
|
Tue Aug 15 10:07:01 2006 |
Alec | 8-ID General | Detectors | chip damage on the new dalsa/smd after surface xpcs |
One week of surface xpcs produced the following (but detector just puit back in beamlne so temperature is still elevated):
 |
|
93
|
Tue Aug 22 10:09:37 2006 |
Mark Sutton | 8-ID General | Controls | Too easy to close wrong shutter |
| Quote: | The open/close shutter buttons on the epics beamline windows are too small
and too close together. I would recommend that each only have its own shutter
bottom, a G user will not accidentally close the I shutter, etc. |
The medm screens will be updated so that A and D shutter control is from the 8-Id screen and I shutter control is from the I screen and E shutter control is from the E and G screen |
|
94
|
Tue Aug 22 15:45:50 2006 |
Alec | 8-ID General | Presentations | ANL ppt template - August 2006 |
|
| Attachment 1: ANLTemplate_Aug2006.ppt
|
|
95
|
Tue Aug 22 16:35:18 2006 |
Alec | 8-ID General | Shutdown Activities | September 2006 |
|
| Attachment 1: Projects_v0-10.xls
|
|
96
|
Wed Aug 23 11:11:48 2006 |
Harold Gibson | 8-ID General | Safety | Updated safety plan |
Here are also some safety related links:
1. APS User Policies and Procedures:
http://www.aps.anl.gov/Users/General_Reference/Policy_Procedures/index.html
2. ANL-E Environment, Safety and Health Manual:
http://www.aim.anl.gov/manuals/eshman/
3. ANL-E Hoisting and Rigging Manual:
http://www.aim.anl.gov/manuals/hoist/index.html
4. ANL-E Transportation Safety Manual:
http://www.aim.anl.gov/manuals/tsm/index.html
5. ANL-E Waste Handling Procedures Manual:
http://www.aim.anl.gov/manuals/whpm/index.html |
| Attachment 1: cat_safty_plan1rev4d_2006.doc
|
|
97
|
Fri Aug 25 13:21:42 2006 |
Alec | 8-ID General | Manuals | Digitel MPC Controller manual |
| The Gamma Vacuum web site has the annoying feature of requiring a login before documentation is made available. So attached is the Digitel MPC manual. |
| Attachment 1: MPC_J.pdf
|
|
100
|
Fri Aug 25 16:42:32 2006 |
Suresh Narayanan | 8-ID General | Manuals | Energy calibration chart from Brookhaven/1-BM |
| Absorption edge plots are attached in a pdf file. It contains sevral edges from 6 kev to 20 kev or so. |
| Attachment 1: Absorption_Energy_calibration_document.pdf
|
|
101
|
Tue Aug 29 18:16:29 2006 |
Suresh Narayanan | 8-ID General | Vendor contacts | KEPCO Contact |
Kepco contact number is:
718-461-7000
software/tech. contact: Bill Yonkers (x5235) |
|
102
|
Thu Sep 7 10:28:12 2006 |
Alec | 8-ID General | Safety | Y2-50 8-ID-A side-bounce mirror review material - Jan. 12, 2006 |
Material presented to the Beamline Safety Design Review Steering Committee (BSDRSC) on Jan. 12, 2006.
Includes raytracing and the like. |
| Attachment 1: AMirrorUpgradeReview.ppt
|
|
103
|
Thu Sep 7 10:33:33 2006 |
Michael | 8-ID General | Safety | 8-ID-D pogo stick upgrade review material - Nov. 7, 2005 |
| Material presented to the Beamline Safety Design Review Steering Committee (BSDRSC) on Nov. 7, 2005. Attachments include Soon Hong's and Michael's presentations. |
| Attachment 1: D_station_monochromator_upgrade.ppt
|
| Attachment 2: Design_Review_D_monochromator_Soon_Hong.pdf
|
|
104
|
Thu Sep 7 10:35:58 2006 |
Michael | 8-ID General | Safety | 8-ID-D pogo stick upgrade review material - Nov. 7, 2005 |
Approval from the BSDRSC (attached)
| Quote: | | Material presented to the Beamline Safety Design Review Steering Committee (BSDRSC) on Nov. 7, 2005. Attachments include Soon Hong's and Michael's presentations. |
|
| Attachment 1: TN05-033_Closeout.pdf
|
|
105
|
Thu Sep 7 10:36:32 2006 |
Alec | 8-ID General | Safety | Y2-50 8-ID-A side-bounce mirror review material - Jan. 12, 2006 |
Approval from the BSDRSC (attached)
| Quote: | Material presented to the Beamline Safety Design Review Steering Committee (BSDRSC) on Jan. 12, 2006.
Includes raytracing and the like. |
|
| Attachment 1: TN05-031_Closeout.pdf
|
|
106
|
Fri Sep 8 11:48:25 2006 |
Suresh Narayanan | 8-ID General | Peltier Device | High temperature Peltier's used |
The High temperature being used at 8-ID are:
1. HT8-7-30
from Melcor (www.melcor.com)
Optimum parameters: 8 V (max) and 6 A (max is 8 A).
Melcor rep. suggested that optimum voltage is 8 V and can go to 6 A. So far, we have been running at 12 V as they had wrong numbers on the data sheet on the web site till 2005.
So the macros have to be changed accordingly.
(Sep. 2006) |
|
107
|
Fri Sep 8 11:49:24 2006 |
Suresh Narayanan | 8-ID General | standard quotations for Beamline Components | Quotes for |
| to be filled in later. |