-
Type: Bug
-
Status: Tested
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 50
-
Component/s: None
-
Labels:None
-
Sprint:DEV-48-3, DEV-48-4, DEV-48-5, DEV-48-RELEASE, DEV-49-1, DEV-49-2, DEV-49-3, DEV-49-4, DEV-49-5, DEV-49-RELEASE, DEV-50-1, DEV-50-2, DEV-50-3, DEV-50-4, DEV-50-5, DEV-50-RELEASE
-
Affect Type:Userdefined
Scenario:
- Save sanger input files (e.g. from the "sanger" folder) to directory with commas "," in path.
- Click "Tools" -> "Sanger data analysis" -> "Maps reads to reference..." and run sanger with files, saved on 1. Declare only one file with reads.
Expected: If you run the same alignment with the same files, located in a directory with comma-separated paths in Workflow Designer, the alignment passes without any problems. This makes me think, that commas (or maybe some other special characters, I haven't checked them all) do not influence the alignment process itself (here I need to remind you, that when you run Sanger alignment with the above-mentioned dialog, it runs in a child process). Probably, the problem appears on some process-preparation step. So, I expect, that this scenario should passes well and without failures after the fix you'll do.
Current: "wrong output format"
- is blocked by
-
UGENE-7902 Unclear "wrong output format" when Sanger alignment fails
- Closed