MOOSE Workshop June 6-8 #23991

GiudGiud · 2023-04-06T01:10:25Z

GiudGiud
Apr 6, 2023
Collaborator

Hi everyone,

We will be holding a MOOSE training/workshop June 6-8 in Idaho Falls.
INL has negotiated discounted hotel rates. There will also be a virtual option to attend.

Please register here:
https://inlhrfedramp.gov1.qualtrics.com/jfe/form/SV_1RDZf244xsF1NK6

Guillaume for the MOOSE team

stu314159 · 2023-05-01T13:20:58Z

stu314159
May 1, 2023

Dear Moose Team,

Are Workshop slots still available? I attempted to follow the link and was presented this message:

6 replies

permcody May 1, 2023
Maintainer

The link is working again. Please register!

stu314159 May 9, 2023

Thank you!

GiudGiud May 10, 2023
Collaborator Author

Link is broken again, will keep you posted!

salaudeen-ya May 10, 2023

I just register now. I think it's fixed.

GiudGiud May 10, 2023
Collaborator Author

nice

ecmLab · 2023-05-14T00:19:54Z

ecmLab
May 14, 2023

I can only attend virtually; is there any agenda available already? Thanks!

1 reply

GiudGiud May 14, 2023
Collaborator Author

Agenda is not available yet. Please register for virtual attendance and it will be sent as soon as we have it

KamalnathOSU · 2023-05-17T16:36:21Z

KamalnathOSU
May 17, 2023

Hi !
Are you planning to record this workshop and make it available on youtube ? The current video on youtube is already 3 years old.
Kamal

1 reply

GiudGiud May 30, 2023
Collaborator Author

Hello

Yes if the recording goes well
We struggled last year with fixing the recording enough to publish it. It's not easy to hold the training hybrid

Guillaume

KamalnathOSU · 2023-06-04T23:35:08Z

KamalnathOSU
Jun 4, 2023

Hi ,
Is there anyway to download the workshop slides locally and view it in a browser ? I want to keep the personal copy of the slides.
Thank you very much.
-Kamal

12 replies

milljm Jun 5, 2023
Maintainer

I too cannot build documentation with the docker image... without some fixes of my own.

GitHub had their keys exposed (forcing everyone to update their root certs). Our Docker image is less than happy due to this. Here are all the commands I had to perform, to make it work (including output):

HOST > docker run -ti idaholab/moose:latest /bin/bash

GUEST > root@fba17ee5aa8a:/opt/moose# export GIT_SSL_NO_VERIFY=1

GUEST > root@fba17ee5aa8a:/opt/moose# git submodule update --init
Cloning into '/opt/moose/large_media'...
Cloning into '/opt/moose/libmesh'...
Skipping submodule 'modules/chemical_reactions/contrib/thermochimica'
Cloning into '/opt/moose/petsc'...
fatal: could not get a repository handle for submodule 'framework/contrib/wasp'

GUEST > root@fba17ee5aa8a:/opt/moose# git submodule deinit -f framework/contrib/wasp
Cleared directory 'framework/contrib/wasp'
error: could not lock config file .git/modules/framework/contrib/wasp/config: No such file or directory
warning: Could not unset core.worktree setting in submodule 'framework/contrib/wasp'
Submodule 'framework/contrib/wasp' (https://code.ornl.gov/neams-workbench/wasp.git) unregistered for path 'framework/contrib/wasp'

GUEST > root@fba17ee5aa8a:/opt/moose# git submodule init framework/contrib/wasp
Submodule 'framework/contrib/wasp' (https://code.ornl.gov/neams-workbench/wasp.git) registered for path 'framework/contrib/wasp'

GUEST > root@fba17ee5aa8a:/opt/moose# git submodule update --init
Cloning into '/opt/moose/framework/contrib/wasp'...
Skipping submodule 'modules/chemical_reactions/contrib/thermochimica'
Submodule path 'framework/contrib/wasp': checked out '827479b89fb5b76a0865974d9f4ca404d55acce0'
Submodule path 'large_media': checked out '26692f4fa6c84545a8b24a138465550043cb6f06'
Submodule path 'libmesh': checked out '5e720a226ba3740dbe92c135936612461f489ada'
Submodule path 'petsc': checked out '477e44bbb558b1357d86363677accbb4bcdfaabc'

GUEST > root@fba17ee5aa8a:/opt/moose#

Now that I have a healthy repo with all the necessary submodules at the right versions checked out... can we attempt to build combined-opt, and then the documentation.

While building the documentation, these are the only errors I receive:

MooseDocs.base.readers (ForkProcess-7): 
TOKENIZE ERROR: Command '['git', 'submodule', 'status', '--recursive']' returned non-zero exit status 128.
/opt/moose/modules/scalar_transport/doc/content/sqa/scalar_transport_sll.md:16

These are normal. The Docker image only contains a shallow copy of the MOOSE repo (in order to keep file sizes down).

I think your error might be related to not having all the necessary submodules checked out at the their correct hashes... I could be mistaken, but the above was all from a fresh install of Docker on my machine, grabbing the latest image.

Can you confirm your submodules are in working order? The following should not work, without some fixes:

cd /opt/moose
git submodule update --init

KamalnathOSU Jun 5, 2023

As you have noted correctly, I am using Docker image. My HPC has only apptainer. Hence, I pulled the docker image and converted into *.sif format.

I dont understand the concept of submodule and dont know whether the submodules are in working order. As the said, the following commands did not work.

[osu7935@pitzer-login02 scripts]$ $DKMOOSE
WARNING: Environment variable LD_PRELOAD already has value [], will not forward new value [/apps/xalt/xalt/lib64/libxalt_init.so] from parent process environment
Apptainer> cd /opt/moose
Apptainer> git submodule update --init
fatal: could not create directory '/opt/moose/.git/modules/large_media'
Failed to clone 'large_media'. Retry scheduled
fatal: could not create directory '/opt/moose/.git/modules/libmesh'
Failed to clone 'libmesh'. Retry scheduled
Skipping submodule 'modules/chemical_reactions/contrib/thermochimica'
fatal: could not create directory '/opt/moose/.git/modules/petsc'
Failed to clone 'petsc'. Retry scheduled
fatal: could not create directory '/opt/moose/.git/modules/large_media'
Failed to clone 'large_media' a second time, aborting
Apptainer>

milljm Jun 5, 2023
Maintainer

My guess is, now that its been converted over to an Apptainer instance, is that you do not have write access to the following location (/opt/). When using Docker, you sign in as root. But the same can not be said with Apptainer. There are switches that allow you to do so that you can try (but I believe certain settings first need to be set on your cluster in order to allow for this feature (/etc/subuid) ref: https://apptainer.org/docs/admin/1.0/user_namespace.html):

apptainer shell --fakeroot /path/to/container.sif

...and then try the git submodule upate --init commands. It should also be mentioned that git submodule update will require network access in order to pull these submodule repos.

If --fakeroot is not available, you can convert your container into a sandboxed one (extract it), and make modifications, etc. The following is not exactly what you want, but the gist of what I do, when I need to "edit" a container:

apptainer build -s /path/to/extracted/container /path/to/container.sif 
cd  /path/to/extracted/container/opt/moose
<do stuff: git submodule, etc while you have write access>
apptainer shell /path/to/extracted/container

Bonus

When all is good, and you like your changes... you can convert this back into a containerized single file:

appatiner build /path/to/new_container.sif /path/to/extracted/container

Edit: Darn, you need --fakeroot to convert it back into a container. But you can still shell "sandboxed" containers without root.

KamalnathOSU Jun 6, 2023

Thank you, Jason @milljm . In our HPC (Ohio supercomputer center), they specifically disabled the fakeroot feature 😢 for the end users.

When I quickly ran your commands, it still gave the same errors. I will dig into it after the workshop. I dont want to make any changes to moose now, which might trigger Murphy's law 😄 and corrupt my HPC setup.
For now, I can compile and create executable which is all I need now.

milljm Jun 6, 2023
Maintainer

Roger that!

I bet after its extracted, there are still perhaps some permissions lingering about (read-only, yet you are the owner: 555 as apposed to 755? or something)

But we can fiddle later when you're ready! The bottom line is, if you're able to apptainer build -s, then there is way :)

KamalnathOSU · 2023-06-06T01:29:03Z

KamalnathOSU
Jun 6, 2023

Dear MOOSE team,
I didn't receive the slack information for the virtual attendees. Was it sent out already or we will get it only tomorrow ?
-Kamal

2 replies

GiudGiud Jun 6, 2023
Collaborator Author

It will be sent again tomorrow if it has not been sent.
Just make sure you have the teams meeting invite

KamalnathOSU Jun 6, 2023

I received the invitation now.

alexlanl · 2023-06-06T05:07:18Z

alexlanl
Jun 6, 2023

Hello!
Sorry, could you please update the registration link again? It doesn’t work.
Thank you!

0 replies

KamalnathOSU · 2024-05-10T21:34:58Z

KamalnathOSU
May 10, 2024

Hi all,

Any update on the MOOSE workshop (in INL) next month ? This time I wish to attend it in person. I registered for it last month but didn't receive any update on that.

Is there any recommended hotels this time ? I wish to book my accommodation and flight a month sooner to avoid high prices.

Thank you,
Kamal

2 replies

GiudGiud May 10, 2024
Collaborator Author

@permcody

GiudGiud May 11, 2024
Collaborator Author

I dont think we have any recommended hotel.
Booking early is smart. Idaho Falls is mostly reachabel by plane. If you travel in a group it can save money to fly to SLC and rent a car from there.

permcody · 2024-05-12T02:40:56Z

permcody
May 12, 2024
Maintainer

I’ll see if we can get any hotel deals set up next week! Last year we weren’t able to do much because we didn’t have a large enough block. As Guillaume said, it’s probably best to book now. If you’ve registered, you are in. We will cut off registration completely when we are fully booked. Cody

…

On Sat, May 11, 2024 at 4:24 AM Guillaume Giudicelli < ***@***.***> wrote: I dont think we have any recommended hotel. Booking early is smart. Idaho Falls is mostly reachabel by plane. If you travel in a group it can save money to fly to SLC and rent a car from there. — Reply to this email directly, view it on GitHub <#23991 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXFOIEXQMSQ23FWWS26P3LZBX5XRAVCNFSM6AAAAAAWUYLG7GVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TGOJUG44DK> . You are receiving this because you were mentioned.Message ID: ***@***.***>

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

MOOSE Workshop June 6-8 #23991

{{title}}

Replies: 8 comments 24 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

MOOSE Workshop June 6-8 #23991

GiudGiud Apr 6, 2023 Collaborator

Replies: 8 comments · 24 replies

permcody May 1, 2023 Maintainer

GiudGiud May 10, 2023 Collaborator Author

GiudGiud May 10, 2023 Collaborator Author

GiudGiud May 14, 2023 Collaborator Author

GiudGiud May 30, 2023 Collaborator Author

milljm Jun 5, 2023 Maintainer

milljm Jun 5, 2023 Maintainer

Bonus

milljm Jun 6, 2023 Maintainer

GiudGiud Jun 6, 2023 Collaborator Author

GiudGiud May 10, 2024 Collaborator Author

GiudGiud May 11, 2024 Collaborator Author

permcody May 12, 2024 Maintainer

GiudGiud
Apr 6, 2023
Collaborator

Replies: 8 comments 24 replies

permcody May 1, 2023
Maintainer

GiudGiud May 10, 2023
Collaborator Author

GiudGiud May 10, 2023
Collaborator Author

GiudGiud May 14, 2023
Collaborator Author

GiudGiud May 30, 2023
Collaborator Author

milljm Jun 5, 2023
Maintainer

milljm Jun 5, 2023
Maintainer

milljm Jun 6, 2023
Maintainer

GiudGiud Jun 6, 2023
Collaborator Author

GiudGiud May 10, 2024
Collaborator Author

GiudGiud May 11, 2024
Collaborator Author

permcody
May 12, 2024
Maintainer