153
edits
Short projects: Difference between revisions
m
→Easy Closes: remove closed bug
(→Easy Closes: removed closed bug) |
m (→Easy Closes: remove closed bug) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
== Implement missing Matlab functions == | == Implement missing Matlab functions == | ||
Use the [https://savannah.gnu.org/patch/?func=additem&group=octave Savannah patch tracker] for submissions unrelated to an existing bug. | * Use the [https://savannah.gnu.org/patch/?func=additem&group=octave Savannah patch tracker] for submissions unrelated to an existing bug. | ||
== Test Octave functions for proper input handling == | |||
* Many functions either do insufficient input checking or the input requirements have changed over time. | |||
* Contributors can try to break Octave function behavior with different types of input, and document the results. | |||
* Users can check <em>expected behavior</em> according to the Octave help and, if applicable, expected compatible behavior according to [https://www.mathworks.com/help/matlab/ public facing Matlab documentation]. | |||
* Inputs to test can be: | |||
** different numeric types - double, single, integer. | |||
** non-numeric types - logical, string, cell, struct | |||
** different input shapes - scalar, row/column vectors, 2D, 3D, & nD arrays, zero size arrays ([], 1x0, and 1x3x0 are all empty but may require different handling). | |||
** char/string parameters: different case handling, partial matching behavior, invalid/nonsense parameters. | |||
* For the input items above, does function behave acceptably? Are numerical or graphical outputs as expected? Is output consistent? Is any error message intelligible/meaningful to the user? | |||
* Optionally the behavior above can be tested against Matlab function output if it is available. If needed but not available, tests can be submitted to other developers for output checking. | |||
** Note 1: There is much undocumented Matlab behavior. Because this has the possibility of changing with little notice, fixing incompatibilities related to such undocumented behavior is considered on a case-by-case basis by the developer team. Documentation of such cases is always beneficial, however. | |||
** Note 2: Only Matlab public documentation and function output may be compared. <em>Internal Matlab code, even if available, should never even be looked at by a contributor. Contributions will be discarded if it is determined such action occurred.</em> | |||
* Contributors can submit bug reports to the [https://savannah.gnu.org/bugs/?group=octave Octave Bug Tracker] documenting their findings. | |||
* An example can be see in bug {{bug|64078}} comment #10 of looking through the /plot/draw functions for how they handle integer and logical inputs to numeric fields. | |||
== Write Built-In Self Tests (BISTs) == | == Write Built-In Self Tests (BISTs) == | ||
| Line 41: | Line 59: | ||
! bug !! bug title !! status | ! bug !! bug title !! status | ||
|- | |- | ||
| {{bug|36954}} || datenum / datevec convert date-time string incorrectly during hour lost to DST || siko1056 suggests closing as won't fix. | | {{bug|36954}} || datenum / datevec convert date-time string incorrectly during hour lost to DST || siko1056 suggests closing as won't fix. nrjank reverted from Postponed to Confirmed / removed Assigned To tag after dormant for 2 years. | ||
|- | |- | ||
| {{bug| | | {{bug|40357}} || OOM when converting from sparse double to sparse logical|| hardy thinks this might be a DUPLICATE, nrjank changed to Need Info, needs better test to determine if the OOM comes from known sparse indexing issue or something else. | ||
|- | |- | ||
| {{bug|48088}} || document that issquare, iscolumn, isempty, etc operate on cell arrays|| documentation patch candidate submitted and needs review. | | {{bug|48088}} || document that issquare, iscolumn, isempty, etc operate on cell arrays|| documentation patch candidate submitted and needs review. | ||
|- | |- | ||
| {{bug|49886}} ||ezplot: octave does not warn when function not vectorized || Rik states This would be easy to fix if {{bug|42691}} was first solved. | | {{bug|49886}} || ezplot: octave does not warn when function not vectorized || Rik states This would be easy to fix if {{bug|42691}} was first solved. That bug was closed as fixed in August 2021, so supposedly this one should now be easier manageable. nrjank marked as Needs Info to determine if desired output is just adding a warning, or also matching matlab output. | ||
|- | |- | ||
| {{bug| | | {{bug|49360}} || odeset lacks documentation for solver options || Needs someone to review and make a to-do list. | ||
|- | |- | ||
| {{bug| | | {{bug|53214}} || area.m needs update to implement ShowBaseline and other properties || nrjank states last remaining task is adjusting the axis limits to fit the data. This has been pushed for area.m. Left remaining is whether to do the same for plot.m which would require checking on/fixing failing tests in other functions. | ||
|- | |- | ||
| {{bug| | | {{bug|54437}} || optimset missing documentation for 5 options || Documentation task. rik states AutoScaling, ComplexEqn, and Updating can be copied from fsolve.m so this would be an improvement. | ||
|- | |- | ||
| {{bug|55065}} || Implement uiopen and uisave || both a patch and m-file versions of the two functions have been separately submitted. they both need to be evaluated for fitness. | | {{bug|55065}} || Implement uiopen and uisave || both a patch and m-file versions of the two functions have been separately submitted. they both need to be evaluated for fitness. | ||