-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
US_Archive utils class #137
Conversation
… to extract function in a clear way
… Edit the doc strings.
…files when they're extracted in the text edit widget
…ve and absolute paths
@samo38 |
@samo38 |
@samo38 |
|
@samo38
I doesn't hurt a lot to have it, just takes a bit longer for the analysis to run. At some point we may push against the limit of container time and have to provide our own container cloud for the analysis, which I'm hoping to avoid. |
Sure! I just add it just in case. Will remove it! somo has its own copy of us_tar in the develop directory. Though it is not called anywhere. |
To use it in the analyze-mpi, I can call us_archive directly instead of editing us_tar or leave it to use us_tar if it's not necessary now. |
I'm concerned about the volume of testing required... lots of clusters, analysis methods etc. |
Places where US_Tar are called:
using system tar:
|
So If you'd prefer to leave us_mpi_analysis to use US_Tar for now, do I delete installing libarchive from github workflow? Although it is quit fast to install it with apt-get. |
I don't see any changes to us_mpi_analysis programs themselves, but the changes did require the codeql apt-get for mpi to succeed. So leave the apt-get for mpi. I think we can migrate us_mpi_analysis to use us_archive, but want to keep it as a separate issue/pull request due to the required testing. This way, we can get your legacy converter in-place and take our time with the us_mpi_analysis. |
Yes you're right! By the way us_mpi_analysis needs the utils to be complied first so libarchive is needed anyway. |
No description provided.