Items to consider turning into Roadmap actionable items

[butlerpd]

The following items are not in a state that they can be translated into an actionable line in the Roadmap but possibly should become so depending on community discussion/input.

• Should the General Scattering Calculator be transitioned to perspective (instead of tools)? It is not truly a perspective on the data since not data is involved but ...?
• How should notebooks be made accessible to the community? storing in a repo? create a web interface like the marketplace? other?
• What should/could be done to improve the unix support/stability. Currently BNL is maintaining a conda package and a group in Australia is maintaining a Debian package version (including in Debian releases)
• Should we revisit the SASfit models integration issue or are we happy with where we are? If revisiting what is the goal/requirements
• Choose better/other graphics package vs matplotlib? (qtplot, pyqtgraph,Silex, other).. or maybe extra for certain tasks? Big issue with matplot lib as I recall is speed? but it is a well known standard and it is used a LOT in SasView so changing completely might be more than we can handle?
• Gen Scattering calculator Bio usability enhancements to include hydration layer, H exchange, dealing with missing H or even fragments from a PDB file - This may be too ambitious to include in the next 5 year roadmap?
• What more needs to be done for complex SLD support?
• From a previous roadmap discussion there was a suggestion that test data used in sasmodel documentation png file should be supplied. Is that necessary? and if so how? the "test data" is generated by SasView using the default parameters given in the documentation so anybody can generate it from the model in principle?

[wpotrzebowski]

At the SAS2022 I was asked about multiple scattering. I don't see we have it on the Road Map but in fact there is some work already done in this topic: https://github.com/SasView/sasmodels/blob/master/sasmodels/multiscat.py.