============= Meeting 21-Mar-2012 =============

For agenda see below minutes.

------------------------ Minutes ----------------------------

Present: BD, MK, GW, MS, GS, TK, DH
Scribe: GW

************
NEW TOPIC: Getting past some sticking points
************

************
RESOLUTION: 
     a. Re "Move location of fieldName from Field to Structure": 
        -> FieldName will go with *Structure* [so, following this change the 
        same introspection interface will be usable for the same Field].  
     b. In Normative Types, re identification of optional fields using "Traits": 
        -> We stay with simple introspection to determine whether optional fields we given.
     c. In Normative Types, re whether pvAccess itself is aware of Ntype id:
        -> No, pvAccess will have no special understanding of a Structure that expresses
           a NType from a Structure that expresses any other system of Fields
     d. Re Unsigned API. 
        -> To reiterate, unsigned will be developed first as Marty's solution [5], 
        after which David can propose API modifications.
************
DH: Nikolay and myself have proposed structures should consist of members which consist of name plus a s a type object. This isn't incoconsistent with PVs knowing there own name.
 
MK: http://epics-pvdata.sourceforge.net/alpha/pvDataPVAccessChanges.html

************ 
 AI on DH by 27th Mar: Add inserstions into MK's proposed changes document
 to illustrate the alternative for moving the introspection interface.
 ************
 
************
NEW TOPIC: Development and Integration of unsigned work
************
************
RESOLUTION: We will create a tag for all sw repos called "beta.1.1", prior to 
beginning work on unsigned and moving Field work.  
************
If someone really wants to release sw prior to completion of the unsigned and 
FieldName move work, then they would branch from tag beta.1.1.

************
AI on MS/GW by Fri 23: Tag all pv*Java and pv*CPP repos beta.1.1.
alphaJava and alphaCPP tagged too. 
************

************
NEW TOPIC: Starting the V4-V3 interop guide
************
GS: Suggests David
MS: his English is great.
BD: Although David's American is awful.

David nominated.
Timo can add example of use of gather.
Greg will write email to them.

GW: Marty is ready to be used?
MK: Yes, note though that it only collects double data [though this is what people
will mostly want]
GW: What's the problem with MASER?
MK: MASER has to be able to save configs of all V4 records [ and it would have
been  convenient to use gather ].
GW: What's the plan for MASER w.r.t gather then?
MK: I'd like to see experience with the gather service before we decide on upgrades.

GW: What's proportion of int type PVs in V3?
MK: very few
GS: Image is an example

GW: Let's leave gather at collecting double for now until we gain experience.


************
NEW TOPIC: easyPVA review (*Marty*)
************
MK: Did anyone manage to run tests?
no, no one did.

GW: Why does intro say "synchronous" interface when EasyMonitor is a method?
MK: I think it can be written so that it works either way. 
There may be two alternatives:
  1. The EasyPVA client provides a callback for monitors
  2. Alternative is to use EasyMonitor setRequester.
 
 MK: Better wording for the Abstract would remove words "is a synchronous" and replace it
 with an indication that callbacks specifically do not have to be used. 

TOPIC WILL CONTINUE NEXT WEEK, AFTER PEOPLE HAVE TESTED EASYPVA.

*********
TOPIC: Archiver interface demo (*David*, 15 mins)
*********
[postponed to next week, gives David time to find out how to share screen on skype]

Meeting ends.


Agenda
-----------

0. Preliminaries (5 mins).

1. Getting past some sticking points (15 mins). 

  Like to propose the following short term assumptions so work can proceed. I think we should
  consider these as working resolutions until we change our minds. Making these assumptions
  allow pvAccess and Normative Types specification publications to proceed:

     a. Re "Move location of fieldName from Field to Structure": 
        -> Fieldname will go with Field, not Structure - ie, as it is now.
     b. In Normative Types, re identification of optional fields using "Traits": 
        -> We stay with simple introspection to determine whether optional fields we given.
     c. In Normative Types, re whether pvAccess itself is aware of Ntype id:
        -> No, pvAccess will have no special understanding of a Structure that expresses
           a NType from a Structure that expresses any other system of Fields
     d. Re Unsigned API. 
        -> To reiterate, unsigned will be developed first as Marty's solution [5], 
        after which David can propose API modifications.
         
  If possible let's just discuss whether we can accept these working assumptions
  rather than trying to formulate alternative decisions.

2. Development and Integration of unsigned work (15 mins).
 
   Should Unsigned changes be made on a branch or 
   other work made on branches. Do we need a beta 1.1 release prior to unsigned changes integration?

3. Starting the V4-V3 interop guide (15 mins).

  Charter deliverable #10 [3]. Really want a document ready by the EPICS meeting, that lays
  out the mechanisms of V4 <-> V3 interop supported now, "medm" solutions, GUI solutions etc. 
  Volunteers needed. I'm lookin at you James.

4. easyPVA review (*Marty*, 30 mins)

  See API proposal [4]
  *Everyone, please check out easyPVA, run examples etc, before meeting.*

5. Archiver interface demo (*David*, 15 mins)