-
Notifications
You must be signed in to change notification settings - Fork 10
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
Abstract for JOSS journal #70
Conversation
Update qiskit_terra version on Dockerfile
Update with recent modification in the Wiki
@toncho11 I have updated the paper with the latest text from the wiki. Please, review when you have time. |
@toncho11 will have little time to work on this abstract. @qbarthelemy or @sylvchev will you be available to review this? |
It's a good idea, but I think that we should publish pyRiemann before. @sylvchev @plcrodrigues @agramfort |
Agreed. |
I am not sure. How much time will take to publish pyRiemann? This risks blocking pyRiemann-Qiskit for a very long time. |
We should consider publishing a JOSS paper on pyRiemann yes. To cite pyRiemann in this paper we can use a zenodo DOI but I am moderately convinced it's useful in the long run. |
Once pyRiemann is published on JoSS, I think we still have time to update the reference to it in this paper. pyRiemann-qiskit is not as mature as pyRiemann and I think it will take some time before it gets published. This is why it may be a good idea to start the process soon, what do you think ? Side question: do you want me to prepare the workflow in pyRiemann repo ? |
Hello. Did you have some time to think about it? |
Ok, I am not sure what action I need to take for this PR now. Shall we proceed or wait for pyRiemann? If yes, is something like the end of november could work? @qbarthelemy |
I asked @alexandrebarachant to have access to zenodo. I don't see anything
happening very soon on pyRiemann otherwise
… Message ID: ***@***.***>
|
Yes, I have a draft for Pyriemann targeting https://jmlr.org/mloss/ that I need to reorganize before sharing. It will happen soon! |
Ok, thank you for the update. I will wait for Zenodo DOI and pyRiemann draft to be ready then. |
let's discuss the target journal to maximize our chances and be in the
right scope.
Sylvain call me ok?
… Message ID: ***@***.***>
|
a few things for me need to be decided first:
- who is onboard? One solution is to add to the paper anyone who
contributed in the past but this deserves some discussion I guess.
- who is leading this? First author? Senior Author?
feel free to voice your opinion
… Message ID: ***@***.***>
|
How did you guys do for |
When we look at the number of lines modified, |
since the last zenodo entry I would say it's me and Quentin mostly who
arrived in the game no?
… Message ID: ***@***.***>
|
I would have kept the first seven contributors. |
add reference to pyRiemann
change affiliation order
This reverts commit 0a4562e.
(this is likely not allowed for security reasons).
Hi, do you have some update with the pyriemann paper? If no, I have referenced the Zenodo DOI of pyRiemann so we could start the submission. |
@gcattan you can now refer to PyRiemann with this bibtex https://github.com/pyRiemann/pyRiemann/blob/master/README.md#how-to-cite |
The full JOSS recommendation are here. Below, the summary:
The compiled PDF version is downloadable as an artifact here.