Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PRE REVIEW]: ELDAM: A Python software for Life Cycle Inventory data management #2735

Closed
whedon opened this issue Oct 9, 2020 · 33 comments
Closed

Comments

@whedon
Copy link

whedon commented Oct 9, 2020

Submitting author: @GustaveCoste (Gustave Coste)
Repository: https://framagit.org/GustaveCoste/eldam
Version: V1.0
Editor: @sjpfenninger
Reviewers: @konstantinstadler, @romainsacchi
Managing EiC: Kristen Thyng

⚠️ JOSS reduced service mode ⚠️

Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.

Author instructions

Thanks for submitting your paper to JOSS @GustaveCoste. Currently, there isn't an JOSS editor assigned to your paper.

The author's suggestion for the handling editor is @sjpfenninger.

@GustaveCoste if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission (please start at the bottom of the list).

Editor instructions

The JOSS submission bot @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type:

@whedon commands
@whedon
Copy link
Author

whedon commented Oct 9, 2020

Hello human, I'm @whedon, a robot that can help you with some common editorial tasks.

⚠️ JOSS reduced service mode ⚠️

Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.

For a list of things I can do to help you, just type:

@whedon commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@whedon generate pdf

@whedon
Copy link
Author

whedon commented Oct 9, 2020

Software report (experimental):

github.com/AlDanial/cloc v 1.84  T=1.82 s (53.8 files/s, 7627.0 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Python                          50           1980           1943           5067
Qt                              10              0              0           3047
SVG                             10              8              6            877
reStructuredText                24            252            199            457
DOS Batch                        2              8              1             30
make                             1              4              6             10
INI                              1              0              0              2
-------------------------------------------------------------------------------
SUM:                            98           2252           2155           9490
-------------------------------------------------------------------------------


Statistical information for the repository '9562c73e5278aa16bc004d02' was
gathered on 2020/10/09.
The following historical commit information, by author, was found:

Author                     Commits    Insertions      Deletions    % of changes
Gustave Coste                  496         28421          19431          100.00

Below are the number of rows from each author that have survived and are still
intact in the current revision:

Author                     Rows      Stability          Age       % in comments
Gustave Coste              8990           31.6         20.0               11.43

@whedon
Copy link
Author

whedon commented Oct 9, 2020

PDF failed to compile for issue #2735 with the following error:

Can't find any papers to compile :-(

@kthyng
Copy link

kthyng commented Oct 9, 2020

@whedon generate pdf from branch joss

@whedon
Copy link
Author

whedon commented Oct 9, 2020

Attempting PDF compilation from custom branch joss. Reticulating splines etc...

@whedon
Copy link
Author

whedon commented Oct 9, 2020

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@kthyng
Copy link

kthyng commented Oct 9, 2020

@sjpfenninger would you be willing to edit this? I see you have 4 currently, but one is about to be wrapped up so I thought it might be ok.

@kthyng
Copy link

kthyng commented Oct 9, 2020

@whedon invite @sjpfenninger as editor

@whedon
Copy link
Author

whedon commented Oct 9, 2020

@sjpfenninger has been invited to edit this submission.

@sjpfenninger
Copy link

@whedon assign @sjpfenninger as editor

@whedon
Copy link
Author

whedon commented Oct 13, 2020

OK, the editor is @sjpfenninger

@sjpfenninger
Copy link

@konstantinstadler 👋 Would you be willing to review this submission to JOSS?

@sjpfenninger
Copy link

@GustaveCoste Thanks for your submission! It looks like there are two broken references in the PDF (and a typo next to one of them: "inteface"). Can you fix those?

@konstantinstadler
Copy link

@konstantinstadler wave Would you be willing to review this submission to JOSS?

Hi, happy to do the review, but can only do that next week.

@GustaveCoste
Copy link

Hi, thank you for initiating the review process. I tried to fix the broken references without success. The strange thing is that I can't see the difference with the example.

Here is the figure:
![Review procedure.\label{fig:review}](review.png)

And the reference to it:
... helps to improve the LCIs quality (\autoref{fig:review}).

Should the figure be inserted before the reference?

@sara-02
Copy link

sara-02 commented Oct 18, 2020

Hey folks, I am available to review more packages, and while this tool is not right up my alley(I work with Python but not software workflow tools), if you need more reviewers for this I am available to help 23rd Oct onwards :)

@sjpfenninger
Copy link

@konstantinstadler Looks like it's next week anyway now, so I'll take you up on the offer. Thanks!

@sjpfenninger
Copy link

Thanks @sara-02, let me see if we find somebody with expertise in the area.

@sjpfenninger
Copy link

@romainsacchi Would you be able to review this submission to JOSS?

@sjpfenninger
Copy link

@whedon add @konstantinstadler as reviewer

@whedon
Copy link
Author

whedon commented Oct 20, 2020

OK, @konstantinstadler is now a reviewer

@sjpfenninger
Copy link

@GustaveCoste Hmm, I'm unsure what's happening there. @openjournals/dev Any idea why following the figure referencing approach from the example does not work in this case?

@arfon
Copy link
Member

arfon commented Oct 21, 2020

@GustaveCoste Hmm, I'm unsure what's happening there. @openjournals/dev Any idea why following the figure referencing approach from the example does not work in this case?

No idea at all sorry. I've been debugging this for the last hour and can't get it to work (I'm currently trying to figure out if this has ever worked 😕). For now, I suggest simply cross-linking manually by just writing out the figure name in the text (e.g. Figure 1 shows...).

@arfon
Copy link
Member

arfon commented Oct 21, 2020

Actually, turns out this is a whitespace issue. If you give your figures some whitespace, e.g., change L65 onward to look like this:

`ELDAM` has been used in various research projects [@Gentil:2020], helping to improve and characterize LCI data quality. Its review procedure has proven very helpful for auditing the LCIs produced by LCA beginners such as interns.

![Review procedure.\label{fig:review}](review.png)

![ELDAM's GUI.\label{fig:gui}](gui.png)

you should find it works.

@romainsacchi
Copy link

romainsacchi commented Oct 21, 2020 via email

@romainsacchi
Copy link

@sjpfenninger yes, I can do that.

@GustaveCoste
Copy link

@arfon Thank you it fixed the problem.

@sjpfenninger
Copy link

@whedon add @romainsacchi as reviewer

@whedon
Copy link
Author

whedon commented Oct 22, 2020

OK, @romainsacchi is now a reviewer

@sjpfenninger
Copy link

Thanks @romainsacchi !

@sjpfenninger
Copy link

@whedon start review

@whedon
Copy link
Author

whedon commented Oct 22, 2020

OK, I've started the review over in #2765.

@whedon whedon closed this as completed Oct 22, 2020
@sjpfenninger
Copy link

@konstantinstadler , @romainsacchi thanks for agreeing to review. Let's head over to #2765 for the actual review!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants