You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will pull down the Roman PITs version of the SFFT archive, and check out the specific branch that (as of this writing) we require. Below, you will make this directory available inside the podman container you'll use to run *phrosty*. (Note: you may prefer to clone `[email protected]:Roman-Supernova-PIT/sfft.git` instead of `https:...`. If you use github with ssh keys, then you already probably know that you want to do this. If not, don't worry about it.)
62
-
63
-
In the future, we will merge the changes we need back to the `master` branch of sfft, but for now, you need the `fixes_20241022` branch.
64
-
65
51
### Get phrosty
66
52
67
53
```
@@ -71,7 +57,7 @@ git checkout main
71
57
cd ..
72
58
```
73
59
74
-
This will pull the actual phrosty code, including the pipeline you'll run. This README file you're reading is within that repository (in `examples/perlmutter/README.md`). The `git checkout main` is probably redundant, becuase it's likely to check that branch out by default. (Again, you may prefer to clone `[email protected]:Roman-Supernova-PIT/phrosty.git`, but you will already know if you want to do that.)
60
+
This will pull the actual phrosty code, including the pipeline you'll run. This README file you're reading is within that repository (in `examples/perlmutter/README.md`). The `git checkout main` is probably redundant, becuase it's likely to check that branch out by default. (Again, you may prefer to clone `[email protected]:Roman-Supernova-PIT/phrosty.git`, but you will already know if you want to do that.) The last `cd ..` puts you back in your parent directory.
75
61
76
62
77
63
### Locate existing directories
@@ -91,13 +77,14 @@ You need to make the following directories. (They don't have to have exactly th
91
77
*`lc_out_dir`
92
78
93
79
In addition, create a directory `phrosty_temp` somewhere underneath `$SCRATCH`, e.g.:
94
-
```mkdir $SCRATCH/phrosty_temp```. (The further examples below will assume that this is where you made it.)
80
+
```mkdir $SCRATCH/phrosty_temp```
81
+
(The further examples below will assume that this is where you made it.)
95
82
96
83
### Populate your sn_info_dir
97
84
98
85
This is where you put information that *phrosty* needs to find information about the OpenUniverse sims, and about any supernova from that sim you want to run it on. The first file you need is `tds.yaml`; copy that file from this directory (i.e. `phrosty/examples/perlmutter/tds.yaml`) into your `sn_info_dir`; when in the `sn_info_dir`, run:)
99
86
```
100
-
cp -p ../phrosty/examples/perlmutter/tds.yaml ./
87
+
cp -p phrosty/examples/perlmutter/tds.yaml ./
101
88
```
102
89
(This file is a modified version of the standard OpenUniverse sims file `/global/cfs/cdirs/lsst/shared/external/roman-desc-sims/Roman_data/RomanTDS`, fixing some paths for our own purposes.)
103
90
@@ -122,7 +109,7 @@ If you look at these `.csv` files, there are four pieces of information on each
122
109
* The pointing of the image
123
110
* The SCA on which the supernova is present for this pointing
after a minute or so, that should log you into one of the nodes with a session that will last 4 hours. (This is overkill; if you know it won't be that long, shorten the time after the `-t` flag.) You can verify that you're on a compute node by running `nvidia-smi`; you should see four different GPUs listed each with either 40MB or 80GB of memory, but no GPU processes running.
136
123
137
-
cd into your "parent" directory.
124
+
cd into your "parent" directory (if you're not there already).
138
125
139
-
Copy the file`interactive_podman.sh` from `phrosty/examples/perlmutter` to your parent directory:
126
+
Copy the files`interactive_podman.sh` and `phrosty_config.yaml` from `phrosty/examples/perlmutter` to your parent directory:
Look at this file. (There's no need to edit it; this is so you can see what's going on.) You'll see number of `--mount` parameters. Each of these takes a directory on the host machine (the `source`) and maps it to a directory inside the podman container (the `target`). For example, you will see your phrosty checkout goes to `/phrosty` inside the container. In addition, a bunch of environment variables are set so that *phrosty* will be able to find all of these directories inside the container.
130
+
Look at the `.sh` file. (There's no need to edit it; this is so you can see what's going on.) You'll see number of `--mount` parameters. Each of these takes a directory on the host machine (the `source`) and maps it to a directory inside the podman container (the `target`). For example, you will see your phrosty checkout goes to `/phrosty` inside the container. In addition, a bunch of environment variables are set so that *phrosty* will be able to find all of these directories inside the container.
144
131
145
132
Now do
146
133
```
@@ -163,6 +150,7 @@ to see how it works, and to see what the various parameters you can specify are.
0 commit comments