OWG Meeting 15-Apr-2009

From GlueXWiki
Jump to: navigation, search

Agenda


Time/Location

1:30 PM Wed 15-Apr-2009 CC F326


To connect by telephone:

1.) dial:

  • 800-377-8846 : US
  • 888-276-7715 : Canada
  • 302-709-8424 : International

2.) enter participant code: 39527048# (remember the "#")


Announcements

Next Meeting

Note the long delay until the next meeting...we may want to reschedule!

The first possible date occurs while I'm at the EPICS meeting in Vancouver, and the following one is during the GlueX collaboration meeting. Thus the next regularly scheduled meeting would occur on 27-May-2009, perhaps a bit too far off. I'll make a proposal for a date before 27-May.


New Action Items from this Meeting

Minutes

Attendees: Elliott W, Simon T, Alex S, Carl T, Vardan G, Eugene C, Fernando B, Beni Z, Mark I, Dave D.


Collaboration Meeting Agenda

  • Suggestion that the Online needs more time.
  • Agenda for budgeted time agreed upon.
  • Online talk by Elliott removed to make more room for electronics and trigger talks.


EPICS Collaboration Meeting

  • Meeting has ~80 participants, 3 days plus tutorial day.
  • Elliott briefly went over his talk (will be posted on DocDb).
  • Elliott bringing a list of questions for EPICS experts.


Online Project List

A long discussion occurred concerning many aspects of the Online effort.

  • Elliott showed some progress organizing project list as to dates and priorities, and will add time estimates to each task.
  • Who will perform all these tasks? Local people have some time, but not much. What role might students play?
  • Generally H-D personnel will maintain everything, so developers must follow H-D guidelines.
  • Online group planned to consist of five people, currently only consists of a (sizable) fraction of Elliott's time.
  • Original estimate is a that 20 man-years effort needed (based on CLAS experience, amongst other things).
  • Long discussion of which EPICS tools to use.
  • Slight bias towards tools in common use at JLab, but only to a point. If much better ones exist they should be used instead. JLab is fairly far behind the rest of the EPICS community in this regard.
  • Use community-supported tools as much as possible, no reason for H-D to invent anything in most cases.
  • Best GUI development tool in wide use is Java/Eclipse-based Control System Studio (CSS).
  • Labview is serious contender for GUI development tool.
  • Many of the best tools come from the Spallation Neutron Source (SNS) at Oak Ridge.
  • SNS uses CSS for all operator screens.
  • SNS uses Labview for many systems, but Labview/EPICS connection used to present information to operators on CSS screens.
  • Few constraints on expert screens. Many will come from manufacturer.
  • Many manufacturers supply Labview control systems for their products.
  • Many questions on role of ECS and how it talks to the rest of the system.
  • AFECS (foundation of ECS) can talk to cMsg and EPICS channel access, amongst other things.
  • We have a CAEN HV mainframe plus a few modules, good candidate for testing gui builders and communications.


Solenoid Coil Tests

  • Mark Stevens will set up three-rack control system in F117, will be moved to Test Lab for coil tests. Will wire according to original design.
  • Mark and Beni will rearrange F117 to make room for control racks.
  • Elliott will try to find three racks (done 16-Apr, ejw).
  • Idea is to outfit racks as in final configuration.
  • Many chassis, modules and signal conditioners need to be purchased. Mark is making list. A-B sales people will be here next week. Possibility of modifying design based on availability of new types of A-B modules.
  • PLC processor and other modules will be used in final system.
  • Controls hardware somehow got left out of H-D budget! Warren Funk and Eugene working to find money.
  • George Bialas working on getting complicated heat exchanger, may piggy-back on another order.


Electronics

Fernando gave an update on FADC125 progress.

  • Should have three full boards in June, including mezzanine cards, giving 72 chan of 12-bit ADC per board.
  • Many tests planned at IUCF and JLab (Electronics group).
Retrieved from "https://halldweb1.jlab.org/wiki/index.php?title=OWG_Meeting_15-Apr-2009&oldid=12803"