-
Notifications
You must be signed in to change notification settings - Fork 3
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
JOSS paper review - Software paper #144
Comments
@PeterKraus thanks for your comments! These are great. I will address these soon. |
#144 (comment) > the reference to the software repo seems unnecessary here (and throughout the paper). The link to the repo is right there in the front-matter!
These have been removed.
Clarified both the encoding and meaning of streamlined as follows: If this is still off, lmk and I can take another stab.
Used "between" instead of to/from
Per your later comment in #146, I added a section to the docs and addressed the 3 points you brought up. Again, lmk if I'm missing something here.
Rewritten:
I'm not aware of an encoder/decoder for crystal structure directly to an image file format. Added the following: |
Thanks, looks great. Please leave the issue open, I'll give it another read tomorrow. |
A couple more comments/suggestions:
|
Hello @sgbaird,
In this issue, I will collate points that relate to the software paper itself. Link to review is: openjournals/joss-reviews#4528
the reference to the software repo seems unnecessary here (and throughout the paper). The link to the repo is right there in the front-matter!
xtal2png/reports/paper.md
Line 45 in cc644f3
the summary is not clear about what is being encoded into what. My understanding is that
xtal2png
can take a coordinate file and create a fingerprint / QR-code-like representation of that coordinate file. If that's the case, it should be more explicit in the summary.xtal2png/reports/paper.md
Line 46 in cc644f3
streamlined results? Is the point here that it feeds well into image-based pipelines?
xtal2png/reports/paper.md
Line 47 in cc644f3
The references in this section on domain transfer make it hard to read. Please rewrite - perhaps put the citations behind the dates.
xtal2png/reports/paper.md
Lines 64 to 67 in cc644f3
Here, rather than to-from, I'd say between coordinate file and png representation (or something similar):
xtal2png/reports/paper.md
Lines 73 to 74 in cc644f3
I am not sure I understand the relevance of Pallette. Please elaborate.
It would be helpful to discuss the technical limitations somewhere. Perhaps it's in the docs, but in my view it could be commented on in the paper:
xtal2png/reports/paper.md
Lines 94 to 97 in cc644f3
First, is there a reason 64x64 pixel image has to be used? I understand it's possible to encode at most 52 atoms within the unit cell. Just by reading the paper, it's not obvious why the cell parameters (lattice constants, angles, volume, point group) occupy rows - seems like a waste of space. If that information was moved into the upper-left zero sector, there would be more space for the pairwise distance matrix.
Second, the issue of 255 possible values is a limitation of the grayscale requirement. If this was lifted, the precision could go up dramatically.
Third, I'm sure there's a good reason for it, but what's the distance matrix for? It can be calculated from the fractional coordinates. If all we want is to do is to represent the CIF file, there's no reason to include it.
I would rewrite this section, as a "potential" time saving is only potential.
xtal2png/reports/paper.md
Lines 105 to 106 in cc644f3
There is no mention of any other software that provides similar functionality. If there truly is not any encoder/decoder for crystal structure to image data, perhaps a short section discussing existing software for molecules and/or textual representation could be included.
The text was updated successfully, but these errors were encountered: