[Feature] Add a new column that shows the data size of the atlas in the Atlas Manager."

[kiratoyoshihara]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When downloading atlases, I sometimes look for ones with a smaller data size so that the download finishes faster. However, I have difficulty determining which atlas will finish downloading more quickly.

Describe the solution you'd like
A clear and concise description of what you want to happen.
Add a new column called data size to the Atlas Manager view.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Append the data size to the atlas name (e.g., Columbia cuttlefile (50μm) 14.0MB).

[alessandrofelder]

I think this is a nice idea @kira1228 . Have you thought about how to get the information without downloading the atlas?

Maybe easiest to tackle this after we tackle brainglobe/brainglobe-atlasapi#179 first?

[kiratoyoshihara]

Hi, @alessandrofelder

I thought that we should include a file named atlas_file_size.csv in the repository, and when launching the atlas manager, retrieve the atlas data sizes from it. Also, what exactly is the GIN repository? I would appreciate it if you could let me know.

[adamltyson]

Also, what exactly is the GIN repository?

This is where we store the packaged atlases (https://gin.g-node.org/BrainGlobe/atlases).

Agree, this likely depends on brainglobe/brainglobe-atlasapi#179, it should be handled on the atlas API side. Eventually, this shouldn't be hosted separately, but is atlas metadata than can be queried before download (see brainglobe/brainglobe-atlasapi#141 (comment)).

IIRC we looked into trying to get the download sizes of atlases before downloading, but it didn't work for every atlas for some reason (@IgorTatarnikov?).

[IgorTatarnikov]

The issue we ran into was the HTTP response from GIN didn't always contain a content-length field (depending if the atlas has been downloaded recently, I think?). I worked around this by scraping the GIN page itself for the estimated file size with this function. This could be used to dynamically fetch the expected download size for each atlas when the widget is instantiated, but knowing GIN it might get grumpy and throttle the requests.