forked from sxs-collaboration/spectre
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Metadata.yaml
397 lines (366 loc) · 13.9 KB
/
Metadata.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
# Distributed under the MIT License.
# See LICENSE.txt for details.
Name: SpECTRE
License: MIT
Homepage: https://spectre-code.org
GitHub: sxs-collaboration/spectre
Version: 2023.07.29
PublicationDate: 2023-07-29
Doi: 10.5281/zenodo.8196313
ZenodoId: 8196313
Description: |
SpECTRE is an open-source code for multi-scale, multi-physics problems
in astrophysics and gravitational physics. In the future, we hope that
it can be applied to problems across discipline boundaries in fluid
dynamics, geoscience, plasma physics, nuclear physics, and
engineering. It runs at petascale and is designed for future exascale
computers.
SpECTRE is being developed in support of our collaborative Simulating
eXtreme Spacetimes (SXS) research program into the multi-messenger
astrophysics of neutron star mergers, core-collapse supernovae, and
gamma-ray bursts.
Keywords:
- Software
- Astrophysics
- General Relativity
- Numerical Relativity
- Multiphysics
- Gravitational Waves
- Discontinuous Galerkin
- Finite Difference
- Finite Volume
Affiliations:
- &aei
Max Planck Institute for Gravitational Physics (Albert Einstein Institute),
Am Mühlenberg 1, Potsdam 14476, Germany
- &caltech
Theoretical Astrophysics, Walter Burke Institute for Theoretical
Physics, California Institute of Technology, Pasadena, CA 91125, USA
- &cornell
Cornell Center for Astrophysics and Planetary Science, Cornell University,
Ithaca, New York 14853, USA
- &coimbra
CFisUC, Department of Physics, University of Coimbra,
3004-516 Coimbra, Portugal
- &fullerton
Nicholas and Lee Begovich Center for Gravitational-Wave Physics and
Astronomy, California State University, Fullerton, Fullerton, California
92831, USA
- &new_hampshire
Department of Physics & Astronomy, University of New Hampshire, 9 Library
Way, Durham NH 03824, USA
- &koln
I. Physikalisches Institut, Universität zu Köln, Zülpicher Straße 77,
50937, Köln, Germany
- &umiss
Department of Physics and Astronomy, University of Mississippi,
University, Mississippi 38677, USA
Authors:
Description: |
We maintain three tiers of authors for the code as a whole: Core, Developers
and Contributors. The full author list for the SpECTRE DOI is built by
concatenating all authors in the order they are listed here.
The primary goal of this author list is to recognize infrastructure work
that does not or cannot have any science papers and results associated with
it. Through authorship on the SpECTRE DOI such work gains recognition that
holds value in academia. Authorship on the SpECTRE DOI does not directly
entitle a person for authorship rights on other publications. Authorship
rights on publications related to SpECTRE are governed by our publication
policy (see `docs/PublicationPolicy.md`).
Note that the placement of authors in these tiers is inherently a subjective
topic since we are forced to compare different projects people work on.
Nevertheless, having guidelines and some way of promoting healthy and
constructive discussions is vital for ensuring the collaborative aspect of
the code is healthy.
Core:
Description: |
For the time a Developer serves as Core developer they take on some
project-management responsibilities, such as initiating and signing off on
code reviews, maintaining compatibility with third-party libraries,
maintaining the CI/CD infrastructure and overseeing the code as a whole.
Guidelines on becoming a Core developer:
- Have at least 4-5 major infrastructure contributions, each taking
roughly 4-5 weeks of full-time work for an existing Core developer.
- Seek out PRs to review and volunteer when calls for a reviewer are
made.
- Reach out to any of the existing Core developers and express your
interest in taking on the responsibilities that come with this role. The
Core developers will discuss the request and either appoint you to Core
developer or provide you with feedback on what they think remains to be
done.
Note that most people will not end up in the Core developer list since a
lot of work will lead to science results and authorship on science papers,
which pay dividends for the work. Supervising students and postdocs does
not count towards Core developer status.
Guidelines on stepping down as Core developer:
- After a Core developer leaves the project they will remain in this tier
for at least two years. At that point the Core developers will discuss
if the person should be moved to the Developer tier.
- A Core developer can step down from the Core developer role at any time.
The author list order is decided by the Core developers.
List:
- Name: Deppe, Nils
Orcid: 0000-0003-4557-4115
Affiliations: [*caltech]
GitHub: nilsdeppe
- Name: Throwe, William
Orcid: 0000-0001-5059-4378
Affiliations: [*cornell]
GitHub: wthrowe
- Name: Kidder, Lawrence E.
Orcid: 0000-0001-5392-7342
Affiliations: [*cornell]
GitHub: kidder
- Name: Vu, Nils L.
Orcid: 0000-0002-5767-3949
Affiliations: [*aei]
GitHub: nilsvu
- Name: Hébert, François
Orcid: 0000-0001-9009-6955
Affiliations: [*caltech]
GitHub: fmahebert
- Name: Moxon, Jordan
Orcid: 0000-0001-9891-8677
Affiliations: [*caltech]
GitHub: moxcodes
- Name: Nelli, Kyle C.
Orcid: 0000-0003-2426-8768
Affiliations: [*caltech]
GitHub: knelli2
Developers:
Description: |
Developers have contributed major features to SpECTRE and remain in this
list indefinitely unless they wish to be removed.
Guidelines on becoming a Developer:
- Do some code review, does not need to be self-initiated.
- Somewhere around 40 commits and 10k-15k lines of code should trigger a
discussion among the Core developers to move someone from Contributors
to Developers. These are guidelines and being above or below these
arbitrary cutoffs does not automatically include or exclude you. E.g.
someone doing complicated low-level code will likely become a Developer
with far fewer lines of code contributed.
- Anyone supervising a Core developer or two Developers may be considered
for Developer status. Whether to be placed as Developer or Contributor
will depend on how active the supervision is. If most of the supervision
is coming from the Core developers then Contributor status is
appropriate. This will be discussed with the person supervising the Core
developer and/or Developers.
This author list is ordered by last name.
List:
- Name: Armaza, Cristóbal
Orcid: 0000-0002-1791-0743
Affiliations: [*cornell]
GitHub: carmaza
- Name: Bonilla, Marceline S.
Orcid: 0000-0003-4502-528X
Affiliations: [*fullerton]
GitHub: mar-celine
- Name: Kim, Yoonsoo
Orcid: 0000-0002-4305-6026
Affiliations: [*caltech]
GitHub: yoonso0-0
- Name: Kumar, Prayush
Orcid: 0000-0001-5523-4603
Affiliations: [*cornell]
GitHub: prayush
- Name: Lovelace, Geoffrey
Orcid: 0000-0002-7084-1070
Affiliations: [*fullerton]
GitHub: geoffrey4444
- Name: Macedo, Alexandra
Orcid: 0000-0001-5139-9013
Affiliations: [*fullerton]
GitHub: macedo22
- Name: O'Shea, Eamonn
Affiliations: [*cornell]
GitHub: osheamonn
- Name: Pfeiffer, Harald P.
Orcid: 0000-0001-9288-519X
Affiliations: [*aei]
GitHub: haraldp271
- Name: Scheel, Mark A.
Orcid: 0000-0001-6656-9134
Affiliations: [*caltech]
GitHub: markscheel
- Name: Teukolsky, Saul A.
Orcid: 0000-0001-9765-4526
Affiliations: [*caltech, *cornell]
GitHub: teukolsky
- Name: Wittek, Nikolas A.
Orcid: 0000-0001-8575-5450
Affiliations: [*aei]
GitHub: nikwit
Contributors:
Description: |
Anyone who has contributed to SpECTRE will be added to this list and
remain a Contributor indefinitely unless they wish to be removed.
Guidelines on becoming a Contributor:
- See our guidelines in `docs/CONTRIBUTING.md` for information on how to
get involved with SpECTRE development.
- Having any PR merged qualifies for this list. If multiple people worked
on the PR together, e.g. several undergraduate students contributing to
a single PR, all persons involved will become a Contributor.
- Supervising a project that results in a merged PR qualifies for this
list. The supervision must be active, i.e. not primarily done by the
Core developers.
- Having an idea for a contribution does not count towards any contributor
status. There must be active supervision of the person(s) implementing
the idea, such as advice on debugging, how to best implement the idea,
etc. The supervision is what will be counted for contributor status.
Generally, a paper is written where the person who came up with the idea
is a co-author, which is how credit is given for the idea. An example is
suggesting "We should try reconstruction scheme X" without continued
guidance throughout the implementation process would not be counted for
contributor status.
This author list is ordered by last name.
List:
- Name: Anantpurkar, Isha
Orcid: 0000-0002-5814-4109
Affiliations: [*cornell]
GitHub: isha1810
- Name: Boyle, Michael
Orcid: 0000-0002-5075-5116
Affiliations: [*cornell]
GitHub: moble
- Name: Carpenter, Alexander
Orcid: 0000-0002-9183-8006
Affiliations: [*fullerton]
GitHub: AlexCarpenter46
- Name: Ceja, Andrea
Orcid: 0000-0002-1681-7299
Affiliations: [*fullerton]
GitHub: acifajkya
- Name: Chaudhary, Himanshu
Orcid: 0000-0002-4101-0534
Affiliations: [*caltech]
GitHub: GitHimanshuc
- Name: Foucart, Francois
Orcid: 0000-0003-4617-4738
Affiliations: [*new_hampshire]
GitHub: ffoucart
- Name: Ghadiri, Noora
Orcid: 0000-0001-9162-4449
Affiliations: [*fullerton]
GitHub: noora-gn
- Name: Giesler, Matthew
Orcid: 0000-0003-2300-893X
Affiliations: [*cornell]
GitHub: mgiesler
- Name: Guo, Jason S.
Affiliations: [*cornell]
GitHub: erfz
- Name: Iozzo, Dante A. B.
Orcid: 0000-0002-7244-1900
Affiliations: [*cornell]
GitHub: "10220"
- Name: Jones, Ken Z.
Orcid: 0009-0003-1034-0498
Affiliations: [*fullerton]
GitHub: "kenzenjones"
- Name: Lara, Guillermo
Orcid: 0000-0001-9461-6292
Affiliations: [*aei]
GitHub: guilara
- Name: Legred, Isaac
Orcid: 0000-0002-9523-9617
Affiliations: [*caltech]
GitHub: isaaclegred
- Name: Li, Dongjun
Orcid: 0000-0002-1962-680X
Affiliations: [*caltech]
GitHub: dongjun826
- Name: Ma, Sizheng
Orcid: 0000-0002-4645-453X
Affiliations: [*caltech]
GitHub: Sizheng-Ma
- Name: Melchor, Denyz
Orcid: 0000-0002-7854-1953
Affiliations: [*fullerton]
GitHub: denyzamelchor
- Name: Morales, Marlo
Orcid: 0000-0002-0593-4318
Affiliations: [*fullerton]
GitHub: MarloMo
- Name: Most, Elias R.
Orcid: 0000-0002-0491-1210
Affiliations: [*caltech]
GitHub: ermost
- Name: Nee, Peter James
Orcid: 0000-0002-2362-5420
Affiliations: [*aei]
GitHub: PunJustice
- Name: Osorio, Alejandro
Orcid: 0009-0000-5024-0086
Affiliations: [*fullerton]
GitHub: ajosorio3
- Name: Pajkos, Michael A.
Orcid: 0000-0002-4983-4589
Affiliations: [*caltech]
GitHub: pajkosmi
- Name: Pannone, Kyle
Orcid: 0009-0005-8607-2113
Affiliations: [*fullerton]
GitHub: Bronoulli
- Name: Ramirez, Teresita
Orcid: 0000-0003-0994-115X
Affiliations: [*fullerton]
GitHub: trami18
- Name: Ring, Noah
Orcid: 0000-0001-6510-4300
Affiliations: [*cornell]
GitHub: nring21
- Name: Rüter, Hannes R.
Orcid: 0000-0002-3442-5360
Affiliations: [*coimbra]
GitHub: hrueter
- Name: Sanchez, Jennifer
Orcid: 0000-0002-5335-4924
Affiliations: [*fullerton]
GitHub: jennifersanchez
- Name: Stein, Leo C.
Orcid: 0000-0001-7559-9597
Affiliations: [*umiss]
GitHub: duetosymmetry
- Name: Tellez, Daniel
Orcid: 0009-0008-7784-2528
Affiliations: [*fullerton]
GitHub: daniel20tellez
- Name: Thomas, Sierra
Orcid: 0000-0003-3574-2090
Affiliations: [*fullerton]
GitHub: sierracthomas
- Name: Vieira, Daniel
Orcid: 0000-0001-8019-0390
Affiliations: [*cornell, *koln]
GitHub: dkvieira
- Name: Wlodarczyk, Tom
Orcid: 0000-0003-0005-348X
Affiliations: [*aei]
GitHub: tomwlodarczyk
- Name: Wu, David
Orcid: 0000-0002-5287-4389
Affiliations: [*cornell]
GitHub: DavidWu421
References:
Description: |
SpECTRE depends on these references. The keys refer to entries in the
'BibliographyFile'. We use BibTeX for our references so we can also cite
them in publications.
BibliographyFile: docs/Dependencies.bib
List:
- Blaze1
- Blaze2
- Charmpp1
- Charmpp2
- Charmpp3
- Gsl
- Hdf5
- Libsharp
- Libxsmm
- MatplotLib1
- MatplotLib2
- NumPy
- Paraview1
- Paraview2
- Pybind11
- Yamlcpp