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

A bug regarding command line parameter parsing conflict. #5

Open
ashesmt0310 opened this issue Mar 13, 2025 · 0 comments
Open

A bug regarding command line parameter parsing conflict. #5

ashesmt0310 opened this issue Mar 13, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@ashesmt0310
Copy link

Describe the bug
In the class CommandLineParserForJuicer.java (which inherits from CommandLineParser.java), the line addBooleanOption('j', "cpu"); overrides the parent class’s definition of addIntegerOption('j', "threads");. This conflict causes the -j short option to be interpreted as a boolean flag (for "cpu") instead of an integer parameter (for "threads"), ​resulting in failure to set the thread count correctly.

To Reproduce
RUN "./scripts/common/juicer_tools apa -j 1 ./work/aligned/inter_30.hic ./work/aligned/inter_30_loops/merged_loops.bedpe ./apa_results"

Expected behavior
The -j or --threads option should accept an integer value (e.g., -j 4) to set the number of CPU threads. The thread pool should initialize successfully with the specified thread count.
But currently, it can only be avoided through the form of --threads 4.

Screenshots
WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.
WARN [2025-03-13T06:35:49,742] [Globals.java:138] [main] Development mode is enabled
Usage: juicer_tools apa [-n minval] [-x maxval] [-w window] [-r resolution(s)] [-c chromosomes] [-k NONE/VC/VC_SQRT/KR] [-q corner_width] [-e include_inter_chr] [-u save_all_data] <hicFile(s)>

Desktop (please complete the following information):

  • OS: Ubuntu 22.04.5 LTS
  • Version: juicer-1.6-0

Additional context
Add any other context about the problem here.

@ashesmt0310 ashesmt0310 added the bug Something isn't working label Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant