What signals does it measure?

Voltage (current)
Voltage of the battery
Position
Temperatures
Hydrophone/Microphone

What do people need to know about Maas Lab?

How do people get to know about Maas Lab?

Can the digital presence of Maas Lab also become physical? How to connect the website back to the river water/current?

Could the server station also become a weather station? Equipped with sensors?

Who will be the gatekeepers/curators of the data?

How to promote lightweight data generation and storage? How to prompt users to (pre)select and (down)edit their data?

Is the display and storage of video really necessary?

What is the minimum amount of necessary documentation? What responsibility does maas lab hold towards its stakeholders?

How can someone contribute to the maas lab database?

Can data points be seen as gestures?

(sensitive observations made by maas lab participants?)

How do we assemble the digital material we collect?

How to keep the connection to the (river) Maas in the display of data?

What open-source systems are there to make use of?

How can we open up the data flow–as a documentation system–for others?

If Maaslab as a project will last for at least 4 more years, what does that mean for data flow?

Could there be a place to install it? Should we first focus on having it installed? Before building the content?

Should we keep Rijkswaterstraat in the loop?

How does the data flow contribute to the broader mission of "new we"?

What are we going to take out even more? And what are we going to add?

Reflect on the process of working with the river.

How do we communicate with Anneke and GJ?

Signal groups and other channels, meetings

MaasLab

Questions:

We want to work at the Maas, what are our accommodation options? When do we want to work?

What should it host?

What's the life-span of what we are building?

3-4 days in winter
Full week in spring

HARDWARE

1. Electronics

Set up raspberry-pi

With working sim module

Find another step up that can power from 2v to 5v

Find a little battery (used phone)

Continue to work with current motor

2. Mechanics

Continue working with belt-less drive

3. Floating structure
Stay with Bamboo?

Reconsider length of structure

Look for a way to lift the pontoon

Make the diameter a little smaller

How much material do you need?

INFORMATION

Documentation

A statically generated website

What could the website be? Markdown file

A link that brings you to YouTube

Trying to be as light as possible

So it works for many people at the same time

Across all scenarios

Link it to other river projects
Link it to sensor data and make some kind of sensorial translation
Some form of process documentation the vlog
We should feel free to make it into a more accessible documentation

~~Scenario 1: Maaslab website~~

+ sensordata

water-current to energy-current translation

Light website - ASCII art website

Scenario 2: Process Blog

it could show sensor data

it should host the process blog itself - have a section about the

Current (4.7v) to current (2.8m/s) to soundwave

Scenario 3: Texting Dataflow bot

You send it a text with a question

What should it respond to and what should it respond with?

How do we document and make sharable the process and outcome?

How do we make space for the DAAR?

As the first work, observing and documenting gatherings and the daar takes place as a series of 'sessions' in time and place and annotations (later reflections on the sessions) - I mean, a blog - in which the entries are presented from multiple perspectives simultaneously, so always in some situated context... first prospectives:

from the viewpoint of an entity floating on the Maas. scores for leaves-sails. media artefacts like postcards going with the ebb and flow of the water surface...
drawn on a canvas (birds-eye overview, but with expanded time domain)
a journal (chronological list-view, entries of events)

Tracing recordings along their branching meandering trajectories, making space for the Quellen (german: sources, but also a spring or origin).

Then filtering possibilities might converge the organisation of Live Archive with the layout potentials of Live Agora. (if we start from where we are here)

the latest internet developments ( Web 3.0) and/or

the impact of technology on society

technological citizenship

the development of digital platforms that function as public space

the ownership of systems and

the artistic and ethical consequences of using artificial intelligence in the design process

different measurement sites
between archive and data-gathering
ritual data and measurable data
algorithm that takes care of voice generation (Maas as speculative narrator...)

The site should be developed in a way that it can be run on a local network, so even disconnected from the internet, and self-hostable (done already in this site :). The syncing can be peer-to-peer, though for now there is a small server in Frankfurt saving our data (texts, media uploads, layouts...).

What if we think through this space as a first step? In a call here with David, imagined this space as a platform for live presentation, moving through the material together.