set .pdf creation

paper.bib

@@ -0,0 +1,37 @@
+@article{Sacchi:2022,
+abstract = {Prospective Life Cycle Assessment (pLCA) is useful to evaluate the environmental performance of current and emerging technologies in the future. Yet, as energy systems and industries are rapidly shifting towards cleaner means of production, pLCA requires an inventory database that encapsulates the expected changes in technologies and the environment at a given point in time, following specific socio-techno-economic pathways. To this end, this study introduces premise, a tool to streamline the generation of prospective inventory databases for pLCA by integrating scenarios generated by Integrated Assessment Models (IAM). More precisely, premise applies a number of transformations on energy-intensive activities found in the inventory database ecoinvent according to projections provided by the IAM. Unsurprisingly, the study shows that, within a given socioeconomic narrative, the climate change mitigation target chosen affects the performance of nearly all activities in the database. This is illustrated by focusing on the effects observed on a few activities, such as systems for direct air capture of CO 2 , lithium-ion batteries, electricity and clinker production as well as freight transport by road, in relation to the applied sector-based transformation and the chosen climate change mitigation target. This work also discusses the limitations and challenges faced when coupling IAM and LCA databases and what improvements are to be brought in to further facilitate the development of pLCA.},
+author = {Sacchi, Romain and Terlouw, T and Siala, K and Dirnaichner, A. and Bauer, C and Cox, B and Mutel, C. and Daioglou, V and Luderer, G},
+doi = {10.1016/j.rser.2022.112311},
+issn = {13640321},
+journal = {Renewable and Sustainable Energy Reviews},
+month = {may},
+pages = {112311},
+title = {{PRospective EnvironMental Impact asSEment (premise): A streamlined approach to producing databases for prospective life cycle assessment using integrated assessment models}},
+url = {https://linkinghub.elsevier.com/retrieve/pii/S136403212200226X},
+volume = {160},
+year = {2022}
+}
+
+@article{Wernet:2016,
+author = {Wernet, G. and Bauer, C. and Steubing, B. and Reinhard, J. and Moreno-Ruiz, E. and Weidema, B.},
+doi = {10.1007/s11367-016-1087-8},
+journal = {The International Journal of Life Cycle Assessment},
+number = {9},
+pages = {1218--1230},
+title = {{The ecoinvent database version 3 (part I): overview and methodology.}},
+url = {http://link.springer.com/10.1007/s11367-016-1087-8},
+volume = {21},
+year = {2016}
+}
+
+@article{Mutel:2017,
+abstract = {Brightway is an open source framework for Life Cycle Assessment (LCA) calculations in Python. The combination of a modular structure, the expressiveness and interactivity of Python and in particular Jupyter notebooks, and tuned calculation pathways allows for new research directions in Life Cycle Assessment. Brightway has been used in papers on meta-analysis of many inventory datasets (Wernet et al. 2011), regionalized LCA (Mutel, Pfister, and Hellweg 2011), and sensitivity analysis (Mutel, Baan, and Hellweg 2013). Brightway consists of three main modules: Brightway2-data (Mutel 2012c) manages how data is stored and accessed; Brightway2-calc (Mutel 2012b) does static and Monte Carlo calculations; and Brightway2-IO (Mutel 2015c) handles the import and export of LCA data from various sources. In addition to these libraries, helper libraries provide documentation and application examples (Mutel 2012a), support for parameterized inventories (Mutel 2015b), and a format for LCA data in arrays (Mutel 2013). A web page (Mutel 2016), documentation (Mutel 2015a), and a development blog (Mutel 2014) are also available.},
+author = {Mutel, Chris},
+doi = {10.21105/joss.00236},
+journal = {The Journal of Open Source Software},
+number = {12},
+pages = {236},
+title = {{Brightway: An open source framework for Life Cycle Assessment}},
+volume = {2},
+year = {2017}
+}

paper.md

@@ -0,0 +1,58 @@
+---
+title: '`pathways`: a Life Cycle Assessment (LCA) approach to characterizing the environmental impacts of transition 
+scenarios'
+tags:
+  - Python
+  - life cycle assessment
+  - prospective
+  - database
+  - premise
+  - scenario
+  - integrated assessment models
+  - energy system models
+
+authors:
+  - name: Romain Sacchi
+    orcid: 0000-0003-1440-0905
+    affiliation: 1
+  - name: Alvaro J. Hahn Menacho
+    orcid: 0000-0003-2592-2186
+    affiliation: 1
+
+affiliations:
+ - name: Paul Scherrer Institute, Villigen, Switzerland
+   index: 1
+
+date: 03 May 2024
+bibliography: paper.bib
+
+---
+
+# Summary
+
+`pathways` is a Python package that characterizes the environmental impacts of products, sectors or transition scenarios
+over time using Life Cycle Assessment (LCA). Compared to traditional scenario results from energy models, `pathways`
+provides a more detailed and transparent view of the environmental impacts of a scenario by resolving supply chains 
+between producers and consumers (as an LCA does). Hence, direct and indirect emissions are accounted for, and 
+double-counting issues are partially resolved.
+
+`pathways` is initially designed to work with data packages produced by premise, but can be used with any IAM scenarios 
+and LCA databases. It reads a scenario and a corresponding set of scenario-based LCA matrices and calculates the 
+environmental impacts of the scenario (or a subset of it) over time.
+
+# Statement of need
+
+# Description
+
+[@Sacchi:2022]
+
+# Impact
+
+# Conclusion and outlook
+
+# Acknowledgements
+
+The authors gratefully acknowledge the financial support from the Swiss State Secretariat for Education, Research and 
+Innovation (SERI), under the Horizon Europe project PRISMA (grant agreement no. 101081604).
+
+# References

workflows/draft-pdf.yml

@@ -0,0 +1,23 @@
+on: [push]
+
+jobs:
+  paper:
+    runs-on: ubuntu-latest
+    name: Paper Draft
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2
+      - name: Build draft PDF
+        uses: openjournals/openjournals-draft-action@master
+        with:
+          journal: joss
+          # This should be the path to the paper within your repo.
+          paper-path: paper.md
+      - name: Upload
+        uses: actions/upload-artifact@v1
+        with:
+          name: paper
+          # This is the output path where Pandoc will write the compiled
+          # PDF. Note, this should be the same directory as the input
+          # paper.md
+          path: paper.pdf