Secundaire tabs
2c. Observers' Feedback [WATERVERSE Project Pilots]: Inzending #8
De pagina Bekijken toont de algemene informatie en gegevens van een inzending. Video bekijken
Details inzending
Inzendingsnummer: 8
ID inzending: 339
Inzending UUID: ac236aac-9e56-435b-b66d-2b31175ad895
Inzending URI: /nl/projects/waterverse/waterverse_pilots_observers_submit
Aangemaakt: vr, 02/16/2024 - 15:35
Voltooid: vr, 02/16/2024 - 16:03
Gewijzigd: vr, 02/16/2024 - 16:03
Extern IP-adres: 194.72.48.162
Ingediend door: Anoniem
Taal: English
Concept: Nee
Huidige pagina: Voltooid
Information and Consent
Target responders: WATERVERSE Pilot Observers
Please, read the Participant Information Sheet and provide your explicit consent below before moving to the pilot participation and feedback provision.
Statement of Informed Consent
Name and Date
Geoff Mandeno
Profile of participant
United Kingdom
South West Water
Water utility
{Leeg}
{Leeg}
Observations
Some tools in the DPPE are not currently able to scale to a level which could deal with real-world use cases in terms of volumes and velocities of incoming data.
It would be good for Iteration 2 if consideration could be given as to how normal users could be enabled to write their own data connectors.
It would be good for Iteration 2 if consideration could be given as to how normal users could be enabled to write their own data connectors.
Documentation for usage of tools is excellent (e.g. pdfs on sharepoint site). However if would be useful to also have more technical information available so it is clear what the tools are actually doing, and how they work "under the hood" so they are not so much black boxes etc. Perhaps just open sourcing the underlying tool code (with comments) would enable this.
Many tools when they fail do not return useful error messages to enable debugging - for example "500 internal server error" etc.
Some of the tools in DPPE do not have associated docs when clicking on the (?) icon, so it is not clear what they do, what they accept as input etc. This makes it hard to consider ways in which DPPE elements could be combined to achieve a data processing goal.
Many tools when they fail do not return useful error messages to enable debugging - for example "500 internal server error" etc.
Some of the tools in DPPE do not have associated docs when clicking on the (?) icon, so it is not clear what they do, what they accept as input etc. This makes it hard to consider ways in which DPPE elements could be combined to achieve a data processing goal.
All active participants in the pilot were engaged and very helpful.
Some tools do not currently scale well to volumes of data we would expect in a real world usage of the tools. This could be problematic if the tools were used at whole of utility network scale.
It would be good to understand in greater detail what all the other operators in DPPE are capable of, and also ways that a more technical user could create their own operator. (This comment is tied in with earlier comments around documentation etc.)
Some tools do not currently scale well to volumes of data we would expect in a real world usage of the tools. This could be problematic if the tools were used at whole of utility network scale.
It would be good to understand in greater detail what all the other operators in DPPE are capable of, and also ways that a more technical user could create their own operator. (This comment is tied in with earlier comments around documentation etc.)
I feel a lot more confident in my understanding and use of the tools following the training. In particular Matteo and Sid were able to talk me through the use of the tools and advise me where I was going wrong.
OK, pilot proceeded smoothly and was concluded ahead of schedule.
{Leeg}
{Leeg}
{Leeg}
Overall I think the WDME is progressing well and in the right direction however further development is needed to make it a more scaleable, well documented and adaptable tool.
Funding Support Agencies