renaming
This commit is contained in:
parent
6b350893fc
commit
f0aeaba61e
2
_toc.yml
2
_toc.yml
@ -18,7 +18,7 @@
|
||||
- file: physicalloss-discuss.md
|
||||
- file: diffphys
|
||||
sections:
|
||||
- file: diffphys-code-gradient.ipynb
|
||||
- file: diffphys-code-burgers.ipynb
|
||||
- file: diffphys-discuss.md
|
||||
- file: diffphys-code-ns.ipynb
|
||||
- file: diffphys-code-sol.ipynb
|
||||
|
@ -588,7 +588,7 @@
|
||||
"\n",
|
||||
"A simple direct reconstruction problem like this one is always a good initial test for a DP solver, e.g., before moving to more complex setups like coupling it with an NN. If the direct optimization does not converge, there's probably still something fundamentally wrong, and there's no point involving an NN. \n",
|
||||
"\n",
|
||||
"Now we have a first example to show similarities and differences of the two approaches. In the section, we'll present a more in depth discussion of these findings, before moving to more complex cases.\n",
|
||||
"Now we have a first example to show similarities and differences of the two approaches. In the section, we'll present a discussion of the findings so far, before moving to more complex cases.\n",
|
||||
"\n",
|
||||
"\n",
|
||||
"## Next Steps\n",
|
||||
@ -599,6 +599,13 @@
|
||||
"* As for the PINN case, you can activate a different optimizer, and observe the changing (not necessarily improved) behavior.\n",
|
||||
"* Vary the number of steps, or the resolution of the simulation and reconstruction.\n"
|
||||
]
|
||||
},
|
||||
{
|
||||
"cell_type": "code",
|
||||
"execution_count": null,
|
||||
"metadata": {},
|
||||
"outputs": [],
|
||||
"source": []
|
||||
}
|
||||
],
|
||||
"metadata": {
|
Loading…
Reference in New Issue
Block a user