[PRE REVIEW]: QUBO for deterministic-8 and flow accumulation: another edge between Quantum Computation and Hydrology

[editorialbot]

Submitting author: @jaimeangola (Jaime Anguiano Olarra)
Repository: https://github.com/jaimeangola/jaimeangola.github.io.git
Branch with paper.md (empty if default branch): qubodet8
Version: v1.0
Editor: Pending
Reviewers: Pending
Managing EiC: Kristen Thyng

Status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/231e76caa8fb0f1b3e254dc3be58e94c"><img src="https://joss.theoj.org/papers/231e76caa8fb0f1b3e254dc3be58e94c/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/231e76caa8fb0f1b3e254dc3be58e94c/status.svg)](https://joss.theoj.org/papers/231e76caa8fb0f1b3e254dc3be58e94c)

Author instructions

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

@jaimeangola if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.

Editor instructions

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

@editorialbot commands

[editorialbot]

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

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

@editorialbot commands

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

@editorialbot generate pdf

[editorialbot]

⚠️ An error happened when generating the pdf.

[editorialbot]

Repository Analysis Report

Code breakdown

github.com/AlDanial/cloc v 1.98  T=0.01 s (656.4 files/s, 114778.8 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Markdown                         3            119              0            675
TeX                              2             51             64            237
Python                           1             11             16             50
YAML                             1              0              0              1
-------------------------------------------------------------------------------
SUM:                             7            181             80            963
-------------------------------------------------------------------------------

Commit Count by Author

61	Jaime Anguiano Olarra
     5	jaimeangola

Repository History

Repository age: First commit on March 03, 2022

Code distribution (top 3 48-hour windows):

Period	Insertions	% of Total	Signal	View Changes
May 05, 2026 - May 07, 2026	2747	89.5%	🔴	View diff
Apr 25, 2024 - Apr 27, 2024	233	7.6%	🟢	View diff
Apr 28, 2026 - Apr 30, 2026	48	1.6%	🟢	View commit

GitHub Activity Metrics

Unable to fetch GitHub activity data

[editorialbot]

Paper file info:

🚨 Wordcount for paper.md is 2471

🔴 Failed to discover a Statement of need section in paper

🔴 Failed to discover a State of the field section in paper

🔴 Failed to discover a Software design section in paper

🔴 Failed to discover a Research impact statement section in paper

🔴 Failed to discover an AI usage disclosure section in paper

[editorialbot]

License info:

🔴 Failed to discover a valid open source license

[kthyng]

Hi @jaimeangola. Is this pointing to the correct branch or do you mean to use the main branch for the code? Currently it is finding 50 lines of code in Python — is that what you intended?

[jaimeangola]

Hi there, See, I am fully open here. I was sharing some thoughts with a former employer of mine and a reviewer of yours, Juan Julian Merelo Guervos, over a manuscript on quantum computation I just wrote and he told me that being code and being free licensed he told me that it definetly should worth a submit to JOSS. Was my first time knowing of JOSS. I have worked lots in free software (GNOME/Mono) decades ago, but till recently I did not come back to coding. The paper is mostly theoretical but it is accompanied with a sample code that fully does what is discussed there. I told JJ that I think JOSS looks more for good chunks of code and of that I have not nothing useful at this time, anyway see that quantum computing still runs and will for many years on very special hardware with propietary hardware. In my time some we chose GNOME against KDE because KDE used Qt, propietary at the time. The rest is history. The code is a very simple file. The core thing is the lagrangian described in the paper which is the core thing when writing this type of code. So it is actually like 70lines of python i guess. Very much like the first genetic algorithm onemax in C# ever written, which I did on suggestion of JJ but never published then. I didn't want to make the same mistake. I hope this explains enough. Thank you for your work.

…

On Sat, May 9, 2026, 00:15 Kristen Thyng ***@***.***> wrote: *kthyng* left a comment (openjournals/joss-reviews#10559) <#10559 (comment)> Hi @jaimeangola <https://github.com/jaimeangola>. Is this pointing to the correct branch or do you mean to use the main branch for the code? Currently it is finding 50 lines of code in Python — is that what you intended? — Reply to this email directly, view it on GitHub <#10559 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYBPZPNPVTJH35OVMXH4BHL4ZZL77AVCNFSM6AAAAACYWUJ2X6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJQGIZDQNBTGE> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jaimeangola]

Hi there, I just wanted to add that yesterday I sent the manuscript to the Journal of Hydrology and is now already available in Elsevier as a preprint in SSRN. I mention this just in case this makes it a reason for you to reject the publication. Thank you. On Sat, May 9, 2026 at 12:30 AM Jaime Anguiano Olarra < ***@***.***> wrote:

…

Hi there, See, I am fully open here. I was sharing some thoughts with a former employer of mine and a reviewer of yours, Juan Julian Merelo Guervos, over a manuscript on quantum computation I just wrote and he told me that being code and being free licensed he told me that it definetly should worth a submit to JOSS. Was my first time knowing of JOSS. I have worked lots in free software (GNOME/Mono) decades ago, but till recently I did not come back to coding. The paper is mostly theoretical but it is accompanied with a sample code that fully does what is discussed there. I told JJ that I think JOSS looks more for good chunks of code and of that I have not nothing useful at this time, anyway see that quantum computing still runs and will for many years on very special hardware with propietary hardware. In my time some we chose GNOME against KDE because KDE used Qt, propietary at the time. The rest is history. The code is a very simple file. The core thing is the lagrangian described in the paper which is the core thing when writing this type of code. So it is actually like 70lines of python i guess. Very much like the first genetic algorithm onemax in C# ever written, which I did on suggestion of JJ but never published then. I didn't want to make the same mistake. I hope this explains enough. Thank you for your work. On Sat, May 9, 2026, 00:15 Kristen Thyng ***@***.***> wrote: > *kthyng* left a comment (openjournals/joss-reviews#10559) > <#10559 (comment)> > > Hi @jaimeangola <https://github.com/jaimeangola>. Is this pointing to > the correct branch or do you mean to use the main branch for the code? > Currently it is finding 50 lines of code in Python — is that what you > intended? > > — > Reply to this email directly, view it on GitHub > <#10559 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AYBPZPNPVTJH35OVMXH4BHL4ZZL77AVCNFSM6AAAAACYWUJ2X6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJQGIZDQNBTGE> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you were mentioned.Message ID: > ***@***.***> >