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
It's great that since #1150 it's possible to download data to a custom directory. However, 'mastDownload' is always appended to the download path even if it isn't the current directory.
It would be nice if there was an option to not do this to keep an existing directory structure cleaner. I was thinking about implementing this myself but it's hard to ensure a good default backwards compatible behavior since the default would change depending the value of the flat flag.
The text was updated successfully, but these errors were encountered:
Thanks for opening this issue! Do you mean that if flat=False, there should be an option to not begin the downloaded filepath with mastDownload? So, for instance, if the download_dir were set to "test", the resulting path would be something like, test/<mission>/<obsid>/<filename> rather than test/mastDownload/<mission>/<obsid>/<filename>.
Yes, that's exactly what I was thinking. For my use case however, I now solved it by downloading the files individually because I'm processing them further after the download.
It's great that since #1150 it's possible to download data to a custom directory. However,
'mastDownload'
is always appended to the download path even if it isn't the current directory.It would be nice if there was an option to not do this to keep an existing directory structure cleaner. I was thinking about implementing this myself but it's hard to ensure a good default backwards compatible behavior since the default would change depending the value of the
flat
flag.The text was updated successfully, but these errors were encountered: