LewisLabUCSD / LewisLabUCSD/GlyCompareCT
Issues with running example data sets
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am attempting to get GlyCompareCT up and running, however, I run into issues in analyzing the example data sets. Here is my most recent error:
(glycompareCT) C:\Users\seaba\GlyCompareCT\Examples>python ../glyCompareCT.py structure -a test1_abd.csv -v test1_var.csv -o test1/ -p glycoCT -b -m integer -c 2
Validating input files...
Traceback (most recent call last):
File "C:\Users\seaba\GlyCompareCT\glyCompareCT.py", line 685, in <module>
main()
File "C:\Users\seaba\GlyCompareCT\glyCompareCT.py", line 54, in main
input_validation(args)
File "C:\Users\seaba\GlyCompareCT\glyCompareCT.py", line 103, in input_validation
assert os.path.isdir(os.sep.join(args.output_directory.split(os.sep)[:-1])), "Invalid output path, check the path: " + os.sep.join(args.output_directory.split(os.sep)[:-1])
AssertionError: Invalid output path, check the path:
Note a directory to test1 has been created but this error is still returned.
My current directory is
`
(glycompareCT) C:\Users\seaba\GlyCompareCT\Examples>dir
Volume in drive C is Windows
Volume Serial Number is A414-7917
Directory of C:\Users\seaba\GlyCompareCT\Examples
2024-05-03 17:28
.2024-05-03 17:29 ..
2024-05-03 17:14 8 196 .DS_Store
2024-05-03 17:14 Jin2017
2024-05-03 17:28 test1
2024-05-03 17:14 28 test1_abd.csv
2024-05-03 17:14 2 084 test1_var.csv
2024-05-03 17:14 28 test2_abd.csv
2024-05-03 17:14 2 084 test2_var.csv
2024-05-03 17:14 42 test3_abd.csv
2024-05-03 17:14 2 084 test3_var.csv
2024-05-03 17:14 28 test4_abd.csv
2024-05-03 17:14 2 084 test4_var.csv
9 File(s) 16 658 bytes
4 Dir(s) 344 891 121 664 bytes free
`
Current conda version is 24.4.0 and current python version is 3.10.14.final.0
platform : win-64
Any help would be greatly appreciated, thanks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the command shown in the issue and the input_validation function in glyCompareCT.py, especially the output-path assertion at line 103. Reproduce the failure on Windows using the listed example CSV files and determine what should happen when the test1 output directory already exists. Done means the example command passes validation and proceeds without the reported invalid output path error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100