taskManeage - Tasks: task #15736, Submitted/published maneaged paper...


You are not allowed to post comments on this tracker with your current authentication level.

task #15736: Submitted/published maneaged paper list

Submitter:  Boud Roukema <boud>
Submitted:  Fri 24 Jul 2020 03:22:04 PM UTC
Should Start On:  Fri 24 Jul 2020 12:00:00 AM UTC Should be Finished on:  Fri 24 Jul 2020 12:00:00 AM UTC
Category:  None Priority:  5 - Normal
Status:  None Privacy:  Public
Assigned to:  None Percent Complete:  0%
Open/Closed:  Open Effort:  0.00

Jump to the original submission

Mon 05 Jul 2021 07:28:44 PM UTC, comment #10: 

The Maneage, Elaphrocentre and Subpoisson papers are all now accepted by their respective journals, CiSE, MNRAS and PeerJ; Maneage and Elaphrocentre are formally published, Subpoisson is still going through proofreading and so on.

A discussion started with this merge request https://gitlab.com/maneage/project-dev/-/merge_requests/7 about how we can allow frequent updates of Maneage'd papers and their publication status without distracting people who want to keep their project updated for software reasons. Currently, we have both:

It seems reasonable to me that for the moment we allow frequent updates of the webpage list, and just do updates of README-hacking.md once in six months or so.

However, we need to have something more bibtex|yaml|jason -like, or even better, something consistent with the Maneage criteria: a conf style convention and a 'make' file to extract the info in html format for about-citation.html, and in plain text for README-hacking.md .

Of course, once we get to say, 20 papers or so, we'll probably want to split off the web text to its own separate page, and this will start looking excessive for README-hacking.md. We currently have 8 papers, 3 of which are clearly branded "Maneage" in the article pdf.

Boud Roukema <boud>
Group Member
Fri 09 Oct 2020 01:37:08 PM UTC, comment #9: 

Congratulations on the paper Boud! The commit has been merged merged into the 'maneage' branch as Commit 04bda5a85b8. I look forward to its acceptance soon :-).

I hope the MNRAS editors see the value in Maneage through such papers and hopefully start recommending it ;-).

Mohammad Akhlaghi <makhlaghi>
Group administrator
Fri 09 Oct 2020 11:46:06 AM UTC, comment #8: 

The elaphrocentre paper is submitted and archived and git-archived :). I've updated the publication list in README-hacking.md on maneage_dev:


In case anyone missed it, MNRAS now has a formal requirement to include a Data Availability Statement at the end of any paper, and there's an informal request to document software availability:


Handling these should be straightforward for any Maneaged paper.

Obviously, it's up to the editor and referee to decide how seriously to take the statements, and up to the community more broadly to decide if it accepts formal statements that more or less say "We couldn't care less. You may beg us for the code if you really think you need it." Let's hope that we raise the standard. :)

Boud Roukema <boud>
Group Member
Wed 29 Jul 2020 04:28:01 PM UTC, comment #7: 

One solution that I had in mind was to have one separate Git project to only "fetch" various published projects that have used Maneage! We just map their "master" branch on their own repository to a branch named by some some fixed reference (maybe arXiv ID?).

This is a good backup of all Maneage-based projects in one separate project and will also make things like extracting their most recent Manage branching easy (we can regularly parse all the branches and fetch any recent commits, then report the values here).

But maybe this should be defined as a separate task, so if anyone is interested they can do it ;-).

Mohammad Akhlaghi <makhlaghi>
Group administrator
Wed 29 Jul 2020 03:42:28 PM UTC, comment #6: 

Thanks for the congrats :).

Regarding the last-common-commit-with-maneage , it's true that people could update and not think of updating the metadata. Maybe we could name the parameter something like "last claimed common commit" rather than listing no known common commit at all? Though I guess that something automatic will probably make more sense in the longer term. It should be easy, though maybe not trivial.

My guess is that a script to do this automatically would have to use diff or one of the variants. I recently found that dwdiff can handle big (100k) text (log) files reasonably while wdiff took 20-30 seconds and I ctrl-C'ed it rather than waiting longer.

I'm not so sure how correctly a diff program would correctly find the most recent common ancestor. Someone should write a script and try... :)

Boud Roukema <boud>
Group Member
Tue 28 Jul 2020 04:22:25 AM UTC, comment #5: 

Congratulations Boud :). It is great to see the ball has started rolling faster!

If I may, I wanted to ask to keep this discussion open for the time being. Git can form the backbone of referencing the projects. Still I think Maneage could have a charactristic reference/search system inside itself.

Mohammadreza Khellat <mkhellat>
Group Member
Mon 27 Jul 2020 11:21:37 PM UTC, comment #4: 

Thanks a lot Boud, I just pushed it as [git.maneage.org/project.git/commit/?id=b3d8fea7010e Commit b3d8fea7010e].

I just removed the last maneage commit from the end of each item. I initially thought it is a good idea too, but the projects can get updated and if they do, we may forget to update it here and there will be confusion. People can always check from the project's Git repository (which we link to) ;-).

Mohammad Akhlaghi <makhlaghi>
Group administrator
Sun 26 Jul 2020 09:19:52 PM UTC, comment #3: 

Congrats for your paper Boud!
No problem for the confusing of my name. I also think that it is a good idea having all Maneaged paper in a list like this :-)

Raul Infante-Sainz <infantesainz>
Group Member
Sat 25 Jul 2020 06:49:25 AM UTC, comment #2: 

Done - I had forgotten that that list was there :)  It's more complete than the list I posted here, though not quite so parseable.




Feel free to squash these together as a single commit.

Raul: sorry about confusing your given name and surname in my first post to this task! :)

Boud Roukema <boud>
Group Member
Sat 25 Jul 2020 02:03:49 AM UTC, comment #1: 

Congratulations on the submission of your paper to arXiv Boud! I just had a fast look! Its the first paper after the publication of the Maneage paper on arXiv :-).

Can you make a commit, adding links to your new paper to 'README-hacking.md', we are currently keeping a Published work using Maneage section there.

But I generally agree with your point in this task on having a more standard place to list published papers. We can also have a webpage on the published papers using Maneage.

Mohammad Akhlaghi <makhlaghi>
Group administrator
Fri 24 Jul 2020 03:22:04 PM UTC, original submission:  

I propose for the moment that we start off the Maneage paper list here in plain text - once there are enough papers we could put them in a .bib file and/or some other reasonable format (e.g. a make configure file :)) in one of the maneage-related git repositories. Or even a new repository, with a name such as maneage-bibliometry .

I've put these including the full URLs, though obviously, URL bases and URL IDs should be separated.

I didn't include the papers where part of the paper is in early versions of the reproduce format.

published-commit is not going to be 100% true - journals normally add proofreading changes and will not update the commit string.

key = Roukema2020
arXiv = https://arxiv.org/abs/2007.11779
git = https://codeberg.org/boud/subpoisson
zenodo = https://zenodo.org/record/3951152
swh = https://archive.softwareheritage.org/swh:1:dir:fcc9d6b111e319e51af88502fe6b233dc78d5166
published-commit =
submitted-commit = 252cf1c
last-common-commit-with-maneage = 25b6fcc
published-doi =

key = Akhlaghi+2020
arXiv = https://arxiv.org/abs/2006.03018
git = https://gitlab.com/makhlaghi/maneage-paper
zenodo = https://zenodo.org/record/3872248
swh =
published-commit = cd47aa9
last-common-commit-with-maneage = db31bce
published-doi =

key = Raul+2020
arXiv = https://arxiv.org/abs/1911.01430
git = https://gitlab.com/infantesainz/sdss-extended-psfs-paper
zenodo = https://zenodo.org/record/3524937
published-commit = 62d83df
last-common-commit-with-maneage = e376731
published-doi = 10.1093/mnras/stz3111

key = Akhlaghi+2015
arXiv = https://arxiv.org/abs/1505.01664
git = https://gitlab.com/makhlaghi/NoiseChisel-paper
last-common-commit-with-maneage = N/A
published-doi = 10.1088/0067-0049/220/1/1

Boud Roukema <boud>
Group Member


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by mkhellat (Posted a comment)
  • -email is unavailable- added by infantesainz (Posted a comment)
  • -email is unavailable- added by makhlaghi (Posted a comment)
  • -email is unavailable- added by boud (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.


    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code