mantidproject / mantid

Main repository for Mantid code
https://www.mantidproject.org
GNU General Public License v3.0
210 stars 122 forks source link

Evaluate deprecated algorithms to remove them/de-deprecate them #31258

Open Pasarus opened 3 years ago

Pasarus commented 3 years ago

During documentation manual testing many deprecated algorithms were found. We need to evaluate whether or not to remove these algorithms or keep them around, and remove the deprecation warning.

The list is:

Some of these algorithms are still used in more recent versions of Mantid, by users, so we need to be sure we can remove these and not negatively impact our users.

RichardWaiteSTFC commented 3 years ago

WISH don't use FindUBUsingMinMaxD (they use FindUBUsingFFT). They do currently have AlignDetectors in powder reduction scripts that aren't maintained by us - so we shouldn't get rid of it till we're sure their scripts have been modified to use ConvertUnits. Probably worth checking both of these with SNS as well.

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs. Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point. If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer. To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs. Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point. If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer. To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.

stale[bot] commented 1 year ago

This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it.