We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New mathematical notations were successfully introduced in #2574.
These changes were introduced in [math_notations.sty](https://github.com/openturns/openturns/blob/master/python/doc/math_notations.sty]. But these notations are not entirely consistent.
openturns/python/doc/math_notations.sty
Line 29 in 7481e77
or:
Line 55 in 7481e77
Line 71 in 7481e77
\set
Line 23 in 7481e77
It is not consistent with the physical input space:
Line 50 in 7481e77
Line 52 in 7481e77
but this could altenatively be named outputDomain.
outputDomain
Update math_notations.sty and the file that use these macros.
No response
The text was updated successfully, but these errors were encountered:
@adutfoy : Do you have any opinion on this topic?
Sorry, something went wrong.
No branches or pull requests
What is the idea?
New mathematical notations were successfully introduced in #2574.
These changes were introduced in [math_notations.sty](https://github.com/openturns/openturns/blob/master/python/doc/math_notations.sty]. But these notations are not entirely consistent.
openturns/python/doc/math_notations.sty
Line 29 in 7481e77
or:
openturns/python/doc/math_notations.sty
Line 55 in 7481e77
or:
openturns/python/doc/math_notations.sty
Line 71 in 7481e77
\set
macro:openturns/python/doc/math_notations.sty
Line 23 in 7481e77
It is not consistent with the physical input space:
openturns/python/doc/math_notations.sty
Line 50 in 7481e77
openturns/python/doc/math_notations.sty
Line 52 in 7481e77
but this could altenatively be named
outputDomain
.Why is this needed?
Update math_notations.sty and the file that use these macros.
Additional Context
No response
The text was updated successfully, but these errors were encountered: