Project

General

Profile

LattPersonality.txt

Kyle Hazelwood, 01/15/2015 12:00 PM

 
1
Issue about H305/307->H304/306 changes - a reminder.
2
In new RR lattice data file there are two dipole trim locations marked H304/306. In past in their places were H305/307. I talked to both Meiqin and Dave J and they confirmed the changes are real.
3
So questions left are If power supply and CAMAC have already properly connected and Data base related changes are made? I 
4
had a look at the second question answer is not yet. 
5

    
6
a way out - a proposal to deal with iregularities in new RR latice 
7
file namings.
8
Currently use lattice data names as 'standard', 
9
For horz from family device R:RRHCOR one have H100-H640 total 104:
10
100-130(16)
11
202-232(16)
12
302-340(20)
13
400-430(16)
14
502-532(16)
15
602-640(20)
16

    
17
But from new lattice data 1)s-val starting at H606,
18
2) 2 extra labbeled as 'HKIC' - HRRK2301,HRRK2302
19
3) H310 have 2
20
4) k400
21
5) H305,307 -> H304,306, if changed accordingly in DB?
22

    
23
Consider this lattice data personality,a Proposal: use the family device definition R:RRHCOR/R:RRVCOR as standard.
24
.read in the device members,extract ced_name
25
.read in lattice data and take the data based on ced_name list.
26
. note that DB recs in pa4196_ced_data assumed the order in
27
ced_name list. 
28

    
29
Questions: 
30

    
31
1. There are two H310, about 7.4 m aprt?
32
2. H305/307 become H304/306. make sure to re-define them in data base.
33
3. In the verticall plane there are total 103 trims. V301 is not in the list ?
34