Experimental Physics and
Industrial Control System

These were the talks we planned for the collaboration meeting
	Properties, events, filters   Bob   15
	Using Data access			Kay   45
	Version4 database 		Marty 45

Core meeting topics to be held Thusday evenning.
	data access handling issues                                       - discussion
	        how it addresses the epics office - and kay's doc.
	        (sales pitch to open office) (Andrew's JAVA implementation of DA)
	how do events get handled - client side - bottom of database.     - discussion
	Protocol                                                          - Jeff

Office people should be at the EPICS core meeting

The raw notes are attached

Notes Sept 13

Read/write access request to data access. Andrew
Can be done when there is an instance	  Jeff
Ralph has a wiki to make this discussion  Jeff
Shared components will be available       Jeff

Type descriptions used in the database are different than channel access
types					 KaY
Not decided - will be an internal one    Jeff
Can provide one --- 			 Jeff
Use the database                         Kay
Can get a description beyond that        Kay
Type code space - returns INT / size int 
Can provide the database one as well     Jeff
Redundant information....
Want a fixed enumerated set		 Kay
Want to support unsigned types		 Jeff
Protocol will support any type space	 Jeff
Need to present this.			 Jeff
Needs to be able to say what the native type Jeff
Start out supporting the database types	 Kay
What about link fields? 
V4 DBD doc says what will be available   Marty
structures, strings, timestamps, enums	 Marty
Andrew's wiki has standard name of the properties Jeff
List will contain all basic types        Kay
Database has distinction between menu and enum - link and structure Kay
To change a link dynamically you need	Marty
	string that is the code to handle it
	structure with data to configue the device
	the dbd interface will get structure / string
Identifier is for the internal use of the datbase. Andrew
Imagines that links has subordinate properties - Andrew
	what kind of link ca, db, hw
	associated - address information
	other subordinate propwerties - PP and MS
should support those over channel access - Andrew
So the new platform should allow this proprty to go across - Jeff/Andrew
What about fields that now have PP property? - Andrew
	TINE server doesn't have this
Introspection should allow this for a field - Jeff
(So we are requiring that the proerties of a field should also be sent?)
How do we implement a get with PP --     Andrew
Not in the API - add ability to add a message - properties Jeff
Get is a one shot subscription - for a flavor - Jeff
Transactions need to be supported - like put with get Kay/Andrew

Does data access already include the browsing and type info? Kay
Added to satisfy MArty's request.
Can user ask for subset of available properties....? Jeff
user does ca_put with property catelog -- ca needs to know this Kay
CA can just send what is requested and the request is denied Jeff
Use traverse in the data container - twice - once for size? once for data?
Can supply reference to property catelog and register a type  Jeff
	client gives back ticket for it (from server)
	uses ticket from then on

writes may not need "dirty bit" compression	Jeff
Want to see protocol before then ---- Andrew
Put it on the wiki--- Jeff

Data access does not tell you what the type is   Kay
-- not checked into CVS
-- new document describes how one would define type Kay
-- doesn't tell you the type
-- browses the type.

Expose types not available publicly.... Kay
Could Jeff check this in?		Kay

Present the most recent idea for data access -- Kay
Attempt to use it			     -- Kay

Sting interface is not well defined          -- Andrew
No string interface to use		     -- Kay

Handle expose types and

Openoffice data access document from Matthias -- MArty
-- they talk about how to support all types --
-- if we are trying to solve the community --   

Data access means property catelog -- Andrew
-- server interface is not yet defined

Need a more developed API for the server side  -- Andrew
-- not how the sever side would use it
-- how would the server side use it

From both the client and server side --

Need a talk on exposing type.....		Kay

Get the diagram of how all of the pieces fit together -   Bob

Jeff to do CVS commit				Andrew
Will send out the string library		Andrew

Prperty catelog for the existing database	Bob
Events and Filters TALK
Read the wiki page that Andrew produced
Deep tree more efficient that wide one

Version 4 database - defining record instances	Marty
-- present this at the meeting

We want to hear what EPICS office people are doing for data interface - Bob

Data access converts to JAVA well		Andrew
Should they adopt data access

45 minutes each.
	Properties, events, filters (15)
	Data access
	Version4 database - 

Core meeting - 
	data access handling issues
	how do events get handled - client side - bottom of database.
	Protocol
	data access -- how it addresses the epics office - and kay's doc.
	(sales pitch to open office) (Andrew's JAVA implementation of DA)

Office people should be at the EPICS core meeting

Propose a schedule - can do it as phone as well.

Phone access to the core meeting.
Provide talks to core members that will not be there.

Replies:

RE: Meeting Notes Jeff Hill

Navigate by Date:

Prev: Data Access / status of CVS repository Ralph Lange

Next: Re: Data Access / status of CVS repository Marty Kraimer

Index: 2002  2003  2004  <2005>  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: RE: Data Access / status of CVS repository ky9

Next: RE: Meeting Notes Jeff Hill

Index: 2002  2003  2004  <2005>  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024