Date   

Re: #correspondencetables - what needs to be done? #correspondencetables

Tiago Morais
 

It is tgmorais1.

Ok ok!


Re: #correspondencetables - what needs to be done? #correspondencetables

Michele De Rosa
 

Great! What's your GitHub usr? I'll add you. Please update the overview file too (see readme in repo)


Re: #correspondencetables - what needs to be done? #correspondencetables

Tiago Morais
 

Hi all,

 

I already finished the correspondence between v3 and v2 of exiobase, but I’m not authorize to upload in the github. Thus, I attached the file year.

 

Meanwhile, I will also start to work on the point 3 from Chris’s list.


Re: #correspondencetables - what needs to be done? #correspondencetables

arthur.jakobs@...
 

Hi Michele,

Like Tiago, I also opted for this group to offer my help.
I added my name to the readme on github and created a pull request.

I will start to work on point 2 from Chris' list.


Re: #correspondencetables - what needs to be done? #correspondencetables

Tiago Morais
 

I will start working on the point 1.

--
Tiago G. Morais
Instituto Superior Técnico - Universidade de Lisboa/University of Lisbon
MARETEC/LARSYS
Área Científica de Ambiente e Energia/Environment and Energy Scientific Area
Departamento de Engenharia Mecânica/Department of Mechanical Engineering
Pavilhão de Mecânica I | Av. Rovisco Pais, 1 | 1049-001 Lisbon, Portugal
Tel: +351 21 841 98 77 | ext. 3877

-----Original Message-----
From: hackathon2019@bonsai.groups.io <hackathon2019@bonsai.groups.io> On Behalf Of Chris Mutel
Sent: 15 de março de 2019 10:44
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] #correspondencetables - what needs to be done?

1. See if there are any differences in the elementary flows lists of exiobase version 2 and 3 (even a single character difference is enough to need a mapping).

2. Map ecoinvent elementary flow list (from
https://github.com/BONSAMURAIS/Correspondence-tables/blob/master/EcoinventElflow3.2_to_ILCD.csv)
to EXIOBASE elementary flow list

3. Map exiobase v3 elementary flow list to US EPA elementary flow list
(https://github.com/USEPA/Federal-LCA-Commons-Elementary-Flow-List/blob/master/fedelemflowlist/output/FedElemFlowList_0.2.csv)

On Fri, 15 Mar 2019 at 11:35, Tiago Morais <tiago.g.morais@...> wrote:

Hi Michele,

I selected to work in this group. How can I help now?

I am also available to have a call Monday.

--
Tiago G. Morais
Instituto Superior Técnico - Universidade de Lisboa/University of
Lisbon MARETEC/LARSYS Área Científica de Ambiente e
Energia/Environment and Energy Scientific Area Departamento de
Engenharia Mecânica/Department of Mechanical Engineering Pavilhão de
Mecânica I | Av. Rovisco Pais, 1 | 1049-001 Lisbon, Portugal
Tel: +351 21 841 98 77 | ext. 3877


-----Original Message-----
From: hackathon2019@bonsai.groups.io <hackathon2019@bonsai.groups.io>
On Behalf Of Chris Mutel
Sent: 15 de março de 2019 10:27
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] #correspondencetables - what needs to be done?

Working group self-assignment is here:
https://bonsai.groups.io/g/hackathon2019/responses?pollid=4642

On Fri, 15 Mar 2019 at 11:20, <@MicDr> wrote:

@Chris Done. Is there anyone that subscribed to this group that is not listed as a group member right now?

@All, I am working on collecting under our group repo all the
info/material/guidelines we have already found/developed on this
topic. Get in touch with me if you have material/ideas

Should we schedule a call sometime early next week (e.g. Monday afternoon 5pm CET) ?



--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################







--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################


Re: #correspondencetables - what needs to be done? #correspondencetables

 

1. See if there are any differences in the elementary flows lists of
exiobase version 2 and 3 (even a single character difference is enough
to need a mapping).

2. Map ecoinvent elementary flow list (from
https://github.com/BONSAMURAIS/Correspondence-tables/blob/master/EcoinventElflow3.2_to_ILCD.csv)
to EXIOBASE elementary flow list

3. Map exiobase v3 elementary flow list to US EPA elementary flow list
(https://github.com/USEPA/Federal-LCA-Commons-Elementary-Flow-List/blob/master/fedelemflowlist/output/FedElemFlowList_0.2.csv)

On Fri, 15 Mar 2019 at 11:35, Tiago Morais
<tiago.g.morais@...> wrote:

Hi Michele,

I selected to work in this group. How can I help now?

I am also available to have a call Monday.

--
Tiago G. Morais
Instituto Superior Técnico - Universidade de Lisboa/University of Lisbon
MARETEC/LARSYS
Área Científica de Ambiente e Energia/Environment and Energy Scientific Area
Departamento de Engenharia Mecânica/Department of Mechanical Engineering
Pavilhão de Mecânica I | Av. Rovisco Pais, 1 | 1049-001 Lisbon, Portugal
Tel: +351 21 841 98 77 | ext. 3877


-----Original Message-----
From: hackathon2019@bonsai.groups.io <hackathon2019@bonsai.groups.io> On Behalf Of Chris Mutel
Sent: 15 de março de 2019 10:27
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] #correspondencetables - what needs to be done?

Working group self-assignment is here:
https://bonsai.groups.io/g/hackathon2019/responses?pollid=4642

On Fri, 15 Mar 2019 at 11:20, <@MicDr> wrote:

@Chris Done. Is there anyone that subscribed to this group that is not listed as a group member right now?

@All, I am working on collecting under our group repo all the info/material/guidelines we have already found/developed on this topic. Get in touch with me if you have material/ideas

Should we schedule a call sometime early next week (e.g. Monday afternoon 5pm CET) ?



--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################







--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################


Re: #correspondencetables - what needs to be done? #correspondencetables

Tiago Morais
 

Hi Michele,

I selected to work in this group. How can I help now?

I am also available to have a call Monday.

--
Tiago G. Morais
Instituto Superior Técnico - Universidade de Lisboa/University of Lisbon
MARETEC/LARSYS
Área Científica de Ambiente e Energia/Environment and Energy Scientific Area
Departamento de Engenharia Mecânica/Department of Mechanical Engineering
Pavilhão de Mecânica I | Av. Rovisco Pais, 1 | 1049-001 Lisbon, Portugal
Tel: +351 21 841 98 77 | ext. 3877

-----Original Message-----
From: hackathon2019@bonsai.groups.io <hackathon2019@bonsai.groups.io> On Behalf Of Chris Mutel
Sent: 15 de março de 2019 10:27
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] #correspondencetables - what needs to be done?

Working group self-assignment is here:
https://bonsai.groups.io/g/hackathon2019/responses?pollid=4642

On Fri, 15 Mar 2019 at 11:20, <@MicDr> wrote:

@Chris Done. Is there anyone that subscribed to this group that is not listed as a group member right now?

@All, I am working on collecting under our group repo all the info/material/guidelines we have already found/developed on this topic. Get in touch with me if you have material/ideas

Should we schedule a call sometime early next week (e.g. Monday afternoon 5pm CET) ?



--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################


Re: #correspondencetables - what needs to be done? #correspondencetables

 

On Fri, 15 Mar 2019 at 11:20, <@MicDr> wrote:

@Chris Done. Is there anyone that subscribed to this group that is not listed as a group member right now?

@All, I am working on collecting under our group repo all the info/material/guidelines we have already found/developed on this topic. Get in touch with me if you have material/ideas

Should we schedule a call sometime early next week (e.g. Monday afternoon 5pm CET) ?

--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################


Re: #correspondencetables - what needs to be done? #correspondencetables

Michele De Rosa
 

@Chris Done. Is there anyone that subscribed to this group that is not listed as a group member right now?

@All, I am working on collecting under our group repo all the info/material/guidelines we have already found/developed on this topic. Get in touch with me if you have material/ideas

Should we schedule a call sometime early next week (e.g. Monday afternoon 5pm CET) ?


Re: Weekly Q&A with Chris

 

Dear all-

The call tomorrow is cancelled so that people (including me) can join the climate strike. You are welcome to send any pressing questions to me directly via email.


Updating the hackathon agenda

 

Dear all-

It is clear that we need to update the agenda, as we have split into working groups with different competencies, and I expect these groups to stick more or less together in Barcelona. I am therefore asking for your ideas, modifications, and wishes for the hackathon agenda. Let your creativity flow!

So far, it seems to me like we will need an intro on Monday morning; and time for zoom conferences to bring in remote collaborators in the morning and late afternoon. These conferences will be a chance for each working group to present their current work for questions and comment, and to set themselves goals for the next 12 hours. Finally, we will have a summing up and strategizing for next steps on Friday afternoon (we will officially end at 14:00 on Friday, though there will be an Apero afterwards).


Re: #softwaremethods Python library skeleton #softwaremethods

 

Dear Brandon, Stefano, and Tomas:

As I did not see much movement from your working group, I have done the following:

Please follow up and complete these deliverables, as people will be reliant on them from the start of the hackathon.


Re: #correspondencetables - what needs to be done? #correspondencetables

 

We have a good start! I added a checklist for pre-hackathon release, and added that to the hackathon planning board.

Michele, please add a short working group description to the hackathon README.


Re: ++for JSON-LD as interchange format

Bo Weidema
 


Re: Meeting #rdf #ontology at 10:00 AM (Zoom connection details attached) #rdf #ontology

 

I agree with Massimo; let me add a few thoughts.

1. There is no perfect schema, or at least we won't find one in the next weeks. So I think at some point it is better to have something with holes than nothing, as the other groups are already starting to write code.

2. Similarly, it would be quite nice to get a interchange format recommendation. You might not think this matters, but if you leave it to us we will all choose different things. Python people like JSON(-LD), but really up to you.

3. I can imagine ending up with multiple repos as we start to write code on conversion to other formats, or validation. But for now your repo is a way to document *how* you came up with what you did. The ontology will be questioned, as there is more than one way of modelling things, and especially LCA people all have their own mental model. So it is especially important to be as transparent as possible (e.g. minutes in formats that are searchable without download).

4. The BEP is the end product of your work - in it, you need to describe your proposal in detail, including what you considered and rejected. Someone should be able to follow the standard by only reading the BEP, though it is allowed in the BEP to reference external material (test cases, reference implementations, examples).


Re: #reproduciblemodels working group - getting organized #reproduciblemodels

 

Thanks Brandon for setting things up so nicely - I very much recommend
reading the repo readme that Brandon wrote if you haven't aready done
this.

We will adapt the scope of this working group as we go along, but let
me give you the motivation for forming it in the first place.

I am increasingly frustrated with the limitations of conventional LCA
formulations. In particular, the assumed linearity and independence of
parameters in the matrices makes little physical sense. Matrices have
a lot going for them, but I see no reason that we can't get the best
of both worlds: correlated, nonlinear sampling for individual product
systems, placed in a larger linear system. Until we come up with a
giant equilibrium model, this is probably a reasonable step forward.

Here are the kinds of things where I personally would like to use
these product system models:
- Parameterized LCIs in ecoinvent
- A model of auto transport which is adapted to load factors, driving
cycle and context, and which correlates fuel inputs with air emissions
- A model of electricity grid mixes which samples from time series
data, getting a much more accurate picture of uncertainty across the
various generation types

But this idea comes with real questions on transparency,
reproducibility, and ease of understanding. This is why I think we
need some standards, best practices, and checklists. I know that
Brandon has already done a lot here, though as far as I understand
this was focused on a specific form of LCI model, not computer models
for LCI (if that makes sense). So, for example, tests are great, but
rarely help transparency, as most unit tests are focused on small
parts of a model or library.

On Thu, 14 Mar 2019 at 11:08, Brandon Kuczenski <bkuczenski@...> wrote:

OK, I added a basic overview to the main README and added you all as contributors to the reproducibility repo. Please commit with wild abandon.

Regarding a call- I am free after 9am US pacific (I think 5pm CET) Thursday or Friday- not unfortunately Thursday night / Friday morning. Another possibility is to use github issues and comments for discussion. First person to open a new issue gets a cigar.

-Brandon
--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################


Re: Meeting #rdf #ontology at 10:00 AM (Zoom connection details attached) #rdf #ontology

Massimo Pizzol
 

Great minutes, thanks for sending them and I look really much forward to next meeting.

 

I’ll try to answer the question below:

 

>>>GitHub repos- BEP 0003 and Deliverables: If we plan to have two different platforms of GitHub. We must clarify on how they would be used by participants in the group. And most importantly avoid duplication of information Action – Ask Chris and Massimo on how they will be used.

  • In the ontology repository we include the deliverables of the WG activities. I.e. all the outputs resulting from the work of the group. For example:
    • The final schema + example (as a link or figure)
    • Minutes of the group meetings (as the one you sent…but in markdown format!)
    • …other products
  • In the Enhancements repository we put:
    • The Ontology BEP (right now it’s here, but once finalized will be then moved here via pull request), which is a meta-level formalization of the process and its results and is collected in the same place as other BEPs.

 

The difference if I understand correctly is that the deliverables are used for operation while the BEP is used for management. Therefore they are separated. This should allow for minimal duplication of information.

This is my understanding at least but please correct me if I am wrong.

Massimo

 

 

 

 


Re: #correspondencetables - what needs to be done? #correspondencetables

 

After some reflection, Brandon's approach is much more sensible than mine.

We would then need to either generate a preliminary vocabulary
ourselves, or get one from the #ontology folks.

Do we know all possible verbs we want to include? For example, in 1-N
mappings do we have a verb for the "default" option?

On Thu, 14 Mar 2019 at 14:49, <@MicDr> wrote:

Thank you Miguel for starting this hashtag and thanks Chris and Brandon for the inputs.

This discussion seems the right place to kick start the Group on Correspondence tables.

I have just created a new directory on GitHub for the work of this sub-group. The link to this discussion is mentioned in the Readme file.

I am currently working on the deliverable I listed under "Before the Hackathon". You will see the updates in the folder soon.

Suggestions and contributions are as always very welcome :)

Mic

--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################


Re: #correspondencetables - what needs to be done? #correspondencetables

Michele De Rosa
 

Thank you Miguel for starting this hashtag and thanks Chris and Brandon for the inputs.

This discussion seems the right place to kick start the Group on Correspondence tables

I have just created a new directory on GitHub for the work of this sub-group. The link to this discussion is mentioned in the Readme file.

I am currently working on the deliverable I listed under "Before the Hackathon". You will see the updates in the folder soon.

Suggestions and contributions are as always very welcome :) 

Mic


Re: Meeting #rdf #ontology at 10:00 AM (Zoom connection details attached) #rdf #ontology

Agneta
 

Hi everyone 

Please find the meeting minutes in the attached document.

A follow- up meeting is planned on Friday 22nd March, 9:00 AM