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
Copy file name to clipboardExpand all lines: README.md
+12-21Lines changed: 12 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,8 +64,7 @@ Instructions for executing the different ExaGO<sup>TM</sup> applications is give
64
64
-[SCOPFLOW](docs/web/scopflow.md)
65
65
-[PFLOW](docs/web/pflow.md)
66
66
67
-
We also provide our user manual as a pdf [manual.pdf](docs/manual/manual.pdf)
68
-
-> need to update this regularly with CI / move to quarto docs.
67
+
We also provide our user manual as a pdf [manual.pdf](docs/manual/manual.pdf).
69
68
70
69
## Tutorials
71
70
@@ -84,7 +83,11 @@ Each application has a different set of options that are described in depth in
84
83
the usage notes. These options can be passed optionally through an options file
85
84
(`-optionsfile <option_file>`), or directly on the command line.
86
85
87
-
Since options may be specified in more than one location (on the command line, and through an options file), it is worth noting that the option specified on the command line supersede those in the options file. For example, if `opflowoptions` options file set the network file via the option `-netfile case9mod.m`, the following behavior occurs:
86
+
Since options may be specified in more than one location (on the command line,
87
+
and through an options file), it is worth noting that the option specified on
88
+
the command line supersede those in the options file. For example, if
89
+
`opflowoptions` options file set the network file via the option
90
+
`-netfile case9mod.m`, the following behavior occurs:
88
91
89
92
```bash
90
93
# This uses case9mod.m
@@ -106,22 +109,11 @@ attempting to contribute. Feel free to raise an issue or contact the team if
106
109
the guidelines are ambiguous or you have a particular question.
107
110
108
111
## Authors
109
-
ExaGO<sup>TM</sup> was designed and implemented by Shrirang Abhyankar. It has
110
-
received significant from following developers:
111
-
- Slaven Peles
112
-
- Nicholson Koukpaizan
113
-
- Maksudul Alam
114
-
- Asher Mancinelli
115
-
- Cameron Rutherford
116
-
- Joshua Hambrick
117
-
- Philip Fackler
118
-
- Eve Tsybina
119
-
- Bruce Palmer
120
-
- Jaelyn Litzinger
121
-
- William Perkins
122
-
- Sayef Azad Sakin
123
-
- Joseph Macam
124
-
- Ryan Danehy
112
+
ExaGO<sup>TM</sup> was designed and implemented by Shrirang Abhyankar and has
113
+
received significant from Slaven Peles, Nicholson Koukpaizan, Maksudul Alam,
114
+
Asher Mancinelli, Cameron Rutherford, Joshua Hambrick, Philip Fackler, Eve
115
+
Tsybina, Bruce Palmer, Jaelyn Litzinger, William Perkins, Sayef Azad Sakin,
116
+
Joseph Macam, and Ryan Danehy.
125
117
126
118
## Acknowledgement
127
119
ExaGO<sup>TM</sup> has been originally developed as a part of
0 commit comments