irmis-devel Mailing List for IRMIS

Hi all,

 

We are thinking of hosting a codathon for IRMIS3 at BNL between March 16
and March 20 (still have to settle on how many days it should be). By
that time we should have a stable candidate for the 3.0.x branch, so we
can meet and beat the hell out of it! Both people who want to know the
inner workings or just use it are welcome. It's a chance for the former
to have a walkthrough of the codebase and for the latter to try
installing, importing data or writing scripts on top of it with faster
feedback from the developer.

 

Let us know if you are interested, so we can make sure we have a big
enough room.

 

Thanks!

Gabriele

Hi all,

 

New release available at:

https://sourceforge.net/project/showfiles.php?group_id=226514&package_id
=274120

 

We hopefully made the final review on the schema for component types: we
added unique constraints and removed a couple of redundant columns. The
Java API was cleaned up and is more self consistent in the naming and
signatures.

 

Full change log at:

http://irmis.sourceforge.net/history.html

 

In the next month I'll concentrate on cleaning up the component and
cables part of the DB/XML and on the client side applications.

 

Gabriele

Hi Eric:

That is exactly the intended purpose.  You are free to define any
'pvgroup' that you want.  (maybe there is a better name than pvgroup).
Then you associate a set of pvs for that pvgroup - for example an alarm
handler group, a set of archiver groups, a set of pvs related to the
linac bpms, etc. No application has been built for this piece of the
schema.

For the lattice, each 'top' element (of type 'sequence') defines a
completely new 'lattice', typically a set of magnet strengths.  We do
not yet have a lattice application - but we are working on the XML
schema. This schema may well have to be adapted.

We will also support the XAL (from SNS Oak Ridge) pvlogger, and SCORE
(save compare and restore) applications.  These are applications that
will take a snapshot of the machine on operator (or timed) request,
which will allow the operator to restore the machine to a previous set
of machine set points.  We have both pvlogger and SCORE running here -
but those point to an SNS type RDB schema.  

Don


> -----Original Message-----
> From: Eric Berryman [mailto:eri...@gm...]
> Sent: Tuesday, December 16, 2008 3:08 PM
> To: irm...@li...
> Subject: [Irmis-devel] New schema questions
> 
> Hello!
> 
> I was looking at the new schema, and I had a few questions:
> 
> - The pv, pvgroup tables ... are these for tagging pvs with system
> names; vacuum, lcw, rf, etc.?  ... just wondering.
> 
> - The element group of tables; is there a way to save the following
> for elements:
>  A specific beam (18 O 3+ 10.89MeV/u)
> -> optics case 1 -> live saveset / date event
>                         -> live saveset / date event
>                         -> other live saves; scans, viewers, etc. /
date event
> -> optics case 2 ->  live saveset / date event
> 
> (48 Ca 8+ 12.3MeV/u)
> -> optics case 1 ->live saveset / date event
>                         -> live saveset / date event
>                         -> other live saves; scans, viewers, etc. /
date event
> -> optics case 2 ->  live saveset / date event
> 
> 
> I'm hoping to be more help in the New Year .. sorry about that.
> Thank you!!!
> Eric
> 
>
------------------------------------------------------------------------
------
> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
> The future of the web can't happen without you.  Join us at MIX09 to
help
> pave the way to the Next Web now. Learn more and register at
>
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.
com/
> _______________________________________________
> Irmis-devel mailing list
> Irm...@li...
> https://lists.sourceforge.net/lists/listinfo/irmis-devel

Hello!

I was looking at the new schema, and I had a few questions:

- The pv, pvgroup tables ... are these for tagging pvs with system
names; vacuum, lcw, rf, etc.?  ... just wondering.

- The element group of tables; is there a way to save the following
for elements:
 A specific beam (18 O 3+ 10.89MeV/u)
-> optics case 1 -> live saveset / date event
                        -> live saveset / date event
                        -> other live saves; scans, viewers, etc. / date event
-> optics case 2 ->  live saveset / date event

(48 Ca 8+ 12.3MeV/u)
-> optics case 1 ->live saveset / date event
                        -> live saveset / date event
                        -> other live saves; scans, viewers, etc. / date event
-> optics case 2 ->  live saveset / date event


I'm hoping to be more help in the New Year .. sorry about that.
Thank you!!!
Eric

Hi all,

 

After months of suffering, we were finally able to make the continuous
build server go through the BNL firewall. Here it is:

 

https://irmis-dev.bnl.gov

 

There you find the continuous build (Hudson) which takes the code after
every commit, builds it, deploys it and tests it. This is going to be
useful when other people will start contributing code (wink wink wink)
so that they can see (and I can see) whether they have broken the build,
or broken some functionality. Right know it's always me that does that.

 

It also has the test instance of the server, so you can go around and
have a look. If you find a bug in the wild, for example, you can see
whether it was already fixed in the development branch. You are free to
go in and play around with the data, remembering one thing: at each
build the data is wiped out. So if you are playing, and suddenly the
data disappears under your feet, well that's what happened.

 

Enjoy!

Gabriele