Cannot open 750Mb Auspice JSON in Chrome #1622
Comments
|
Which browser are you using? Your issue sounds similar to #1499. In general, I recommend using the |
|
Thank you so much @joverlee521, you are right Firefox works pretty fine ! I did not notice that solution. |
|
Maybe we could add a warning in Export if the file is bigger than what Chrome will tolerate, say 500 MB, and suggest to minify. |
|
Hi @corneliusroemer. Sure ! That would help a lot ! |
victorlin
changed the title
victorlin
added
enhancement
Based on feedback from @jameshadfield in #56 (comment) Looking at the existing dataset files on S3, the 5 KiB root-sequence.json is pretty negligible when the main Auspice JSON is only 163 KiB. Nextstrain datasets are limited by the 500MB memory cap in Chrome,¹ so we'd be fine adding the root sequence inline. ¹ nextstrain/auspice#1622
Based on feedback from @jameshadfield in nextstrain/zika#56 (comment) Looking at the existing dataset files on S3, the 5-6 KiB root-sequence.jsons are pretty negligible when the main Auspice JSONs are 600-800 KiB. Nextstrain datasets are limited by the 500MB memory cap in Chrome,¹ so we'd be fine adding the root sequence inline. This ensures that our uploads will include the root sequence so that they don't get out-of-sync with the main Auspice JSON. ¹ nextstrain/auspice#1622
Based on feedback from @jameshadfield in nextstrain/zika#56 (comment) Looking at the existing dataset files on S3, the 8 KiB root-sequence.json is pretty negligible when the main Auspice JSON is only 163 KiB. Nextstrain datasets are limited by the 500MB memory cap in Chrome,¹ so we'd be fine adding the root sequence inline. ¹ nextstrain/auspice#1622
Based on feedback from @jameshadfield in nextstrain/zika#56 (comment) Looking at the existing dataset files on S3, the 8 KiB root-sequence.json is pretty negligible when the main Auspice JSON is only 163 KiB. Nextstrain datasets are limited by the 500MB memory cap in Chrome,¹ so we'd be fine adding the root sequence inline. This ensures that our uploads will include the root sequence so that they don't get out-of-sync with the main Auspice JSON. ¹ nextstrain/auspice#1622
|
Between nextstrain/augur#1155 and nextstrain/augur#1331, I think the original problem has been solved — closing this out. |
victorlin
changed the title
|
As mentioned in nextstrain/augur#1155 (comment), it's still worth adding a warning in Auspice for large JSONs. The discussion in this issue is mostly around a specific example though, so I've updated the title. Re-opened another issue for adding the warning and closing nextstrain/augur#1155. |
Hi everyone,
Cannot open a *.json file in https://auspice.us/. My file is about 750Mb (2400 monkeypox complete genomes). I ran augur pipeline more than 5 times trying to solve the issue and I never received a warning message, my pipeline runs good and produces a final "right" file. I made a test with only 600 monkeypox genomes (retrieving json file about 25mb) and auspice.us works well (it opens the file with any problem). Is there any limit size to upload in auspice.us ?
Please find attached the drive link to check my files, my compressed *json file is "ns_monkeypox_221222.rar". You will find my metadata.tsv, auspice_config.json, lat_longs.tsv, raw_tree.nwk, refine_tree.nwk
https://drive.google.com/drive/folders/1zHeNQCCkTndamhUpay_VxPAyBJLnEZ4W?usp=share_link
Please, I would appreciate you to help me with this issue.
The text was updated successfully, but these errors were encountered: