-
Notifications
You must be signed in to change notification settings - Fork 1
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
DYAMOND summer initial conditions #64
Conversation
3ff71f0
to
74cca40
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, read the documentation and see the other examples on how to add artifacts.
In this, keep in mind that the key point of ClimaArtifacts is to ensure that everything is reproducible, so we provide automated scripts to generate artifacts (including the download).
I tried using the |
This sounds like a bug. I'll try recreating locally. The one thing I can think of that might cause such a behavior is creating the tarball, but that should not even happen for such a large file. At what stage did it crash?
Yes, the script does other things too. We don't want upload an artifact like the one that you added for a few reasons:
To solve problems 1-3, the script defines a notion of "downloadable" and "undownloadable" artifacts and treat them differently. The script also prompts you to take certain actions (or not). For example, in this case, we would not upload the file to box. In addition to that, When possible, the script also verifies that |
I ran this code and it worked without problems on my machine:
Output:
|
Can the
In this case, it downloaded the |
I reran both versions of the code, with |
|
I am not sure what's going on here. The code up to that point is extremely
simple (only three lines of code: download, mv, and cp). Can you try
running the cp command from your repl
https://github.com/CliMA/ClimaArtifacts/blob/52fec71bf569f46b2e722b4cde6d2d47d26672e6/ClimaArtifactsHelper.jl/src/ClimaArtifactsHelper.jl#L208
(And check that the paths in the function are correct)
It should very easy to debug what goes wrong (you don't have to re-download
the file every time for these tests)
…On Sat, Nov 9, 2024, 10:19 AM Sriharsha Kandala ***@***.***> wrote:
julia --project create_artifact.jl
┌ Warning: atmos_dyamond_summer already exists. Content will end up in the artifact and may be overwritten.
└ @ ClimaArtifactsHelper ~/work/ClimaArtifacts/ClimaArtifactsHelper.jl/src/ClimaArtifactsHelper.jl:195
┌ Warning: Abort this calculation, unless you know what you are doing.
└ @ ClimaArtifactsHelper ~/work/ClimaArtifacts/ClimaArtifactsHelper.jl/src/ClimaArtifactsHelper.jl:196
[ Info: ifs_oper_T1279_2016080100.nc not found, downloading it (might take a while)
ERROR: LoadError: IOError: sendfile: no space left on device (ENOSPC)
Stacktrace:
[1] uv_error
@ ./libuv.jl:100 [inlined]
[2] sendfile(dst::Base.Filesystem.File, src::Base.Filesystem.File, src_offset::Int64, bytes::Int64)
@ Base.Filesystem ./filesystem.jl:153
[3] sendfile(src::String, dst::String)
@ Base.Filesystem ./file.jl:1004
[4] cp(src::String, dst::String; force::Bool, follow_symlinks::Bool)
@ Base.Filesystem ./file.jl:386
[5] cp
@ ./file.jl:378 [inlined]
[6] create_artifact_guided_one_file(file_path::String; artifact_name::String, file_url::String, append::Bool)
@ ClimaArtifactsHelper ~/work/ClimaArtifacts/ClimaArtifactsHelper.jl/src/ClimaArtifactsHelper.jl:208
[7] top-level scope
@ ~/work/ClimaArtifacts/atmos_dyamond_summer/create_artifact.jl:9
—
Reply to this email directly, view it on GitHub
<#64 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACF6E7NLT3DUKLJMCB3FNLTZ7ZG27AVCNFSM6AAAAABRMFN4AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWGM4DQMBYHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
works well. However,
tries to create a huge file that eventually uses up all the space on the hard drive. |
This sounds like an issue with Julia Base, can you open at issue on their GitHub page? |
Using
I made a PR #69 with the change. |
5b5843e
to
17681fc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you remove the change in ClimaArtifactsHelper.jl (we can discuss it in the other PR), squash the commits, and add a link to the main readme?
Yes. That's the plan. I wanted to first check if this works correctly! |
`Base.cp` seems to have a bug when copying large files. Using `run` fixes this behaviour. This fixes the bug mentioned in #64
`Base.cp` seems to have a bug when copying large files. Using `run` fixes this behaviour. This fixes the bug mentioned in #64
b35e86f
to
28d6fe6
Compare
Done. |
28d6fe6
to
f05e131
Compare
Upload DYAMOND summer initial conditions.
Checklist:
$artifact_name
README.md
in that that folder thatLICENSE
fileProject.toml
and
Manifest.toml
)OutputArtifacts.toml
file containing the informationneeded for package developers to add
$artifact_name
to their package/groups/esm/ClimaArtifacts/artifacts/$artifact_name
)Overides.toml
on the Caltech Cluster(in
/groups/esm/ClimaArtifacts/artifacts/Overrides.toml
)README.md
to point to the new artifact