building-envelope-data / api

API specification to exchange data about building envelopes
MIT License
3 stars 1 forks source link

Assist to define the methods from raw hygrothermal data to the data sets used by planning software #292

Open christoph-maurer opened 1 year ago

christoph-maurer commented 1 year ago

IBP and CERROlutions define the methods. ISE should define the framework.

simon-wacker commented 1 year ago

I'm a bit lost. What I understand from the title is that there is hygrothermal data in some raw format. What does "raw" mean here? Is it for example time-series data in CSV-format or HDF or ... Now, this data shall be converted to other formats used by planning software. Is there is a list of planning software (and corresponding formats) that would be nice to be supported and ones that shall be supported by the end of the project? The conversion shall take place using methods as a service and the methods themselves are developed by IBP and CERROlutions. And ISE shall "define the framework". I don't understand what this means. Does it mean that the ISE thinks about and formalizes an architecture in which these methods as services live (are deployed)? Does ISE also implement this architecture? Does it also formalize and implement the plumbing needed to make the methods developed by IBP and CERROlutions accessible as services?

christoph-maurer commented 1 year ago

Thank you for your questions! After the kickoff, I see clearer.

What I understand from the title is that there is hygrothermal data in some raw format. What does "raw" mean here? Is it for example time-series data in CSV-format or HDF or ...

We don't know which formats c3rro already has. I think that they use JSON for their data, but that they still need to develop schemas as an extension of https://github.com/building-envelope-data/api/tree/develop/schemas .

Now, this data shall be converted to other formats used by planning software.

I hope that c3rro takes care of the methods from raw measurement data sets to data sets which can be used by planning software.

Is there is a list of planning software (and corresponding formats) that would be nice to be supported and ones that shall be supported by the end of the project?

Yes, WINDOW from LBNL shall be able to use the hygrothermal data at the end of the project.

The conversion shall take place using methods as a service and the methods themselves are developed by IBP and CERROlutions.

No, the methods don't need to be implemented as a service. If they want to implement methods as a service, they can use the planned reference implementation of a method as a service together with the planned extension of this repository for methods as a service.

And ISE shall "define the framework". I don't understand what this means. Does it mean that the ISE thinks about and formalizes an architecture in which these methods as services live (are deployed)?

Yes, we should think about the architecture in graphql. c3rro can use it if they want for methods as service.

Does ISE also implement this architecture?

I think it's enough that ISE extends the API specification and the reference implementation of a data server.

Does it also formalize and implement the plumbing needed to make the methods developed by IBP and CERROlutions accessible as services?

No, we cannot formalize and implement the plumbing of methods with which we are not familiar.