[Halld-controls] JInventory and slot number

[Elliott Wolin]

Hi,

Hovanes makes a very good case for doing what I at first thought wasn't 
a good idea.  It's also less work for me from a development point of 
view, but means more work for everyone else, i.e. having to enter more 
information into the database (not a big deal in my opinion, especially 
given the "save as new" feature).

So, if you have an opinion, what do you think..should we include slots 
as separate items in the database, with housing parent, power parent, 
etc, supplying housing, power, etc. to a module?

Thanks,




On 05/10/2012 10:19 AM, Hovanes Egiyan wrote:
> Hi Elliott,
>
> when I was exercising with IRMIS I actually used slot as
> a location type housed by the chassis, powered by the chassis,
> and controlled by the controller in the crate. Note that
> controller may or may not be housed by a slot, so it was one
> of the cases of different ordering of items in the three hierarchies.
> Same inversion applied for instance to the power supply of the crate 
> which can
> be considered to be inside the crate, controlled by something else,
> powered from the power strip, while the crate is powered by the power 
> supply.
>
> I do not see why "slot" is not a good item like a crate.  The housing
> hierarchy for A-B channel would be something like this:
> Bldg->[Floor]->Rack->Crate->Slot->Signal
>
> Hovanes.
>
>
> On 05/10/2012 09:50 AM, Elliott Wolin wrote:
>> Hi,
>>
>> Josh asked for a telecom field in the JInventory system, which I 
>> added.  In discussion with him we realized we need a place to put a 
>> slot number or range of slot numbers.
>>
>> The housing hierarchy holds the parent id, so e.g. the parent of an 
>> A-B module will be an A-B chassis.  But where to keep the slot 
>> number?  I was planning to eliminate the five location tables.  I 
>> could replace it with a single "location" field, but one that 
>> wouldn't be unique (there will be many slot 5's).  I could add a 
>> "slot" field specifically for this where you could enter a slot or 
>> range of slots (e.g. "5" or "1-2").
>>
>> Specifying a parent is adequate for many but not all cases.  E.g. the 
>> parent of an A-B chassis will be another entry corresponding to a 
>> rack.  But there is no point in entering "slots" as independent 
>> entries in the database.  Thus the need for an additional field.  
>> "Slot" may suffice, maybe "location" is better, not sure...
>>
>> Thoughts?  Suggestions?
>>

-- 

				Sincerely,
					Elliott


================================================================================


  Those raised in a morally relative or neutral environment will hold
		    no truths to be self-evident.
				

Elliott Wolin
Staff Physicist, Jefferson Lab
12000 Jefferson Ave
Suite 8 MS 12A1
Newport News, VA 23606
757-269-7365

================================================================================