|
|
SONOPA Consortium Meeting 2 15th and 16th of October 2013 in Paris Minutes Web: 1FE39924EA7434AD7D29734F76 |
DAY 1
- WP2 User requirements
A. WP2 D2.1: Getting to know the users
Explore and specify
the user requirements
Goal: input for design and architecture of SONOPA
How?
- By using scientific
literature, earlier AAL-projects, Interview and focus groups
- Focus on fairly
healthy and independent end-users
* Process of SONOPA, points that need to be dealt:
- Communication
- Clear deadlines for feedback
- How can we avoid further delay?
- The
interview is about open questions and then depending on the participant’s
response we will ask further (the probes leading the discussion)
- Insist:
why? Why no or why yes? We need to know the reasons. For instance, would you
accept some sensors in a room? No, why?
- How
explain the relation between the monitoring of the end-user and the social
network: the sensors will enable the entourage to know how these persons are
going and what they are doing and they give an opportunity to the family,
friends etc. to contact and care about the user
- What we want to be
SONOPA’s outcomes? What a reviewer of the EC expects from SONOPA? We should be
able to measure the outcomes that will be aimed.
- Attention, we
should also show the benefits of the visual sensors (and not only ask what they
think about the visual sensors)
B. WP2 D2.2 Ethical Methodologies Report
- Deadline 31/10/13
and feedback of partners before 21/10/13
-
Attention: In chapter 7, remove the phrase regarding “any cameras/visual
sensors will not be used” – as in the first data collection phase those will be
deployed.
C. Presentation of the technical
architecture
- We need to ask from
the end-user: what kind of social network they would like to use
***
- Be very
specific in the internal review mails: which partners must read the document
and before which deadline
***
2. Technical
presentation about activity and mobility analysis based on low-resolution image
sensors and PIR sensor networks
- Low-level sensory
data analysis to high-level activity and behavior modeling of the user
- Research setup in
our lab at the GU
- These sensors don’t need wires but in the
research phase we would use wires
- Still some quality
problems but its doing to be solved
- These visual
sensors will enable us to gather data
- We won’t recognize
the persons but just identify their presence
- Mouse cam sensors
network that will be activated by the PIR sensors:
1. Low-resolution
image sensors
2. PIR sensor
networks
What can we get from mouse cam network:
Low-level behavioral statistics
- Hot spots in the room
- Activity level per time unit
- Tracklet statistics
Extract high-level information
- Health related parameters
- E.g. quantity changes in sleeping, eating and walking patterns
Two different analyses:
1) Single camera analysis (silhouette detection, space detection…)
2) Multi-camera analysis (hot spot detection,
Future plan
Mouse cam to be set
up in a service flat in Belgium
Capture video data of
elderly people in their home
Set up communication
between the server and the client
Sensors to be used
- PIR sensors (Smart
Signs) – an Internet connection
needed (strength in doors 13m and a routers can be used in order to
increase the strength). Detecting if someone is there or not.
- Low-resolution
image sensors (Iminds)
- Camera and touch
screen (Camera Contact): The camera is integrated in the screen so the
screen should be on the table. As a result, we could integrate the option
of telephone conferences. In the screen, some webpage interfaces can be
intergrated (but not web-browsers). The users could choose whether the
camera is on or off.
- Door openers (Abotic): we
can drive any data that we wish with these sensors.
- And other equipment to be foreseen, for instance equipment sensors
(oven on/off).
> The question of budget, we need to see what the
EC will approve.
> All these
sensors will be tested in a test flat in Belgium
DAY2
3. Function blocks
vs. user scenarios
|
Doors sensors |
Abotic |
|
PIR sensors |
Smart Signs |
|
Camera+microphone+touch
screens |
Camera Contact |
|
Applicance status
sensors |
iMinds |
|
Furniture seniors |
Smart Signs |
|
SONOPA CONTROLLER |
|
|
Data model |
CCC (other people involved in the sensors to
provide data) |
|
Sensors middleware
+ Storage |
SmS, ST UT |
|
Activity
Recognition (types of activities: presence,
motion patterns) |
UD |
|
Advice database |
Leave it for
scenarios |
|
Human interface (touch screen, alerts, video-conference) |
SmS, CCC |
|
Touch screens |
|
|
Cloud |
|
|
Social network |
|
|
SN Infrastructure |
UD (DO,UD, ST UT) |
|
Social Connection
Analysis |
UD |
|
Social Connection
Recommendation |
UD |
Note: All the partners must fill in their
timesheets on the platform regarding their tasks.
T3.1 Social Network
Infrastructure and User interface
What are the minimum
requirements for the SN? Calls, personal wall
- Discussion about
the Advisory Committee of the project
- This committee is
formed by technical experts, end-users representatives, companies
- Project will me
promoted during different international meetings
- All partners will
propose some names for end-user organizations, spin offs and universities
- WP5
Communication and Exploitation
- All conferences and
workshops that the partners participated should be reported for the other
participants (inform WP leader about the AAL Forum)
- Next meeting: June
2014 (in 7 months related for the WP): Bilbao, Spain