Bug introduced in 10.1.0 and fixed in 10.2.0
Some problem in v10.1.0 (Windows 8.1 x64) and the new MinMax
...
MinMax[{0.2`, 0.375`, 0.55`, 0.7250000000000001`, 0.9000000000000001`,
1.`, 0.2`, 0.9`, 1}]
{0.2, 1.}
Now
Needs["NDSolve`FEM`"]
MinMax[{0.2`, 0.375`, 0.55`, 0.7250000000000001`, 0.9000000000000001`,
1.`, 0.2`, 0.9`, 1}]
MinMax[{0.2, 0.375, 0.55, 0.725, 0.9, 1., 0.2, 0.9, 1}]
This happens because NDSolve FEM MinMax
shadows the newly added System MinMax
and because NDSolve FEM MinMax
doesn't supports mixed Integer
and Real
arguments.
Of course, it's better to be specific always:
System`MinMax[{0.2`, 0.375`, 0.55`, 0.7250000000000001`,
0.9000000000000001`, 1.`, 0.2`, 0.9`, 1}]
{0.2, 1.}
UPDATE
Hello,
Thank you for contacting Wolfram Technical Support. The mentioned conflict is a known issue and our developers are aware of it. I have added your contact information to the existing report so you can be notified when this is resolved. Thank you once again for taking the time and bringing this to our attention. Sincerely,
[...]
Wolfram Technical Support Wolfram Research http://www.wolfram.com/support/
NDSolve`FEM
package is loaded. Then the user would know to use the full name. $\endgroup$NDSolve`FEM`
afterSystem`
in$ContextPath
. For exampleNeeds["NDSolve`FEM`"]; $ContextPath = RotateLeft[$ContextPath]
is an easy way. Of course it gives the FEM functions the lowest priority, but maybe that's ok. $\endgroup$