You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did something a little silly, but it exposed a poor error message:
# 1090008640.ms
birli *gpubox* -m *.metafits -u 1090008640.ms
# prints out
thread 'main' panicked at 'couldn't initialise uvfits writer: IO(Os { code: 21, kind: IsADirectory, message: "Is a directory" })', src/main.rs:1036:14
(I'm using the v0.5.0 branch and it failed on the line containing .expect("couldn't initialise uvfits writer"))
This error happens because the "file" already exists, and Rust notes that this is a directory when trying to initialise the output as a file. It would be good to have existing files checked and handled in this case, but also user input filenames checked; .ms files write as MS, .uvfits write as uvfits, etc.
The text was updated successfully, but these errors were encountered:
I did something a little silly, but it exposed a poor error message:
(I'm using the v0.5.0 branch and it failed on the line containing
.expect("couldn't initialise uvfits writer")
)This error happens because the "file" already exists, and Rust notes that this is a directory when trying to initialise the output as a file. It would be good to have existing files checked and handled in this case, but also user input filenames checked; .ms files write as MS, .uvfits write as uvfits, etc.
The text was updated successfully, but these errors were encountered: