windows中，
通过 python -m venv生成的虚拟环境，
在dos窗口中，通过activate.bat激活虚拟环境，
执行虚拟环境scripts目录中的python.exe，
实际执行的却是C:\Users\username\AppData\Local\Programs\Python\中的python
这可能是pytorch的DataLoader，当num_workers大于0时，出错的原因。
https://github.com/microsoft/WSL/issues/10032
>wsl --unregister ubuntu
followed by
>wsl --install
fixes the problem for ubuntu atleast
Change the location of the standard Python libraries. By default, the libraries are searched in prefix/lib/pythonversion and exec_prefix/lib/pythonversion, where prefix and exec_prefix are installation-dependent directories, both defaulting to /usr/local.
When PYTHONHOME is set to a single directory, its value replaces both prefix and exec_prefix. To specify different values for these, set PYTHONHOME to prefix:exec_prefix.
Augment the default search path for module files. The format is the same as the shell’s PATH: one or more directory pathnames separated by os.pathsep (e.g. colons on Unix or semicolons on Windows). Non-existent directories are silently ignored.
In addition to normal directories, individual PYTHONPATH entries may refer to zipfiles containing pure Python modules (in either source or compiled form). Extension modules cannot be imported from zipfiles.
The default search path is installation dependent, but generally begins with prefix/lib/pythonversion (see PYTHONHOME above). It is always appended to PYTHONPATH.
An additional directory will be inserted in the search path in front of PYTHONPATH as described above under Interface options. The search path can be manipulated from within a Python program as the variable sys.path.
C:\MDAL> git push
Username for 'https://github.com': user007
Password for 'https://user007@github.com':
Everything up-to-date
从master分支切换到mike21_mesh_optimize分支
C:\MDAL> git status
On branch mike21_mesh_optimize
nothing to commit, working tree clean
C:\MDAL> git push
fatal: The current branch mike21_mesh_optimize has no upstream branch.
To push the current branch and set the remote as upstream, use
git push --set-upstream origin mike21_mesh_optimize
To have this happen automatically for branches without a tracking
upstream, see 'push.autoSetupRemote' in 'git help config'.
If the bathymetry level in an element is above the minimum depth cutoff value then the minimum depth cutoff value is replacing the actual bathymetry value in the computations. Please note that the minimum depth cutoff value may be negative as the bathymetry levels is often so in the mesh file.
If you also apply a Datum shift - the depth cutoff is relative to the corrected depths.
For instance - you have a mesh file with values between +2 and -20 meters. You then shift these to a different datum with a shift of +1 meters. Your corrected bathymetry now ranges between +1 and -21 m. You can then cutoff all depths above -2m, leaving the bathymetry used in the model to range between -2 and -21 m.
原因：使用正则表达式分析数据造成 regex_split
