canSAS-XI/Software - Revision history

Butler: /* Summary */

2019-07-11T18:53:32Z

Summary

← Older revision		Revision as of 18:53, 11 July 2019
Line 20:		Line 20:
	** Add citations and activity etc for each software package listed on the canSAS portal page could be a great help in making whats available more accessible		** Add citations and activity etc for each software package listed on the canSAS portal page could be a great help in making whats available more accessible
	** Would also be good if most highly used packages moved to top so people don't have to always read through the entire list.		** Would also be good if most highly used packages moved to top so people don't have to always read through the entire list.
	* There is probably a need for special workflows for focused problems that give users the 2-3 parameters they are looking for.		* Correlative Analysis
	* ~~If all~~ packages are designed as scriptable ~~first~~ they can ~~then more easily~~ be pulled into various ~~frameworks to develop different workflows for different communities for example or in~~ frameworks for correlative/multi-modal analysis. We should try to encourage all package writers to do this. It is really the correct way to be writing software anyway.		** Should not reinvent the wheel but use existing packages for each technique
			** Tools to do this exist and could be put together (with work) but some math/research needs to be done into how to handle the relative weighting from each technique properly
			** There is probably a need for special workflows for this to be practical - Actually workflows for focused problems that give users the 2-3 parameters they are looking for could be useful for a number of user commutnities.
			** As long as packages are designed as scriptable they can readily be pulled into various frameworks for correlative/multi-modal analysis. They could also be incorporated into different workflows for different communities. We should try to encourage all package writers to do this. It is really the correct way to be writing software anyway.
	* Securing funding for long term maintenance and funding		* Securing funding for long term maintenance and funding
	** Can we reposition analysis software as infrastructure. In Europe there is an evolving new infrastructure funding model which would support infrastructure indefinitely (presumably as long as it is a useful infrastructure?)		** Can we reposition analysis software as infrastructure. In Europe there is an evolving new infrastructure funding model which would support infrastructure indefinitely (presumably as long as it is a useful infrastructure?)
Line 28:		Line 31:
	*** This would probably require collaboratively maintaining and developing the critical packages and/or infrastructure. That would require getting everyone with any effort in SAS analysis software identified and together to discuss “infrastructure” support models.		*** This would probably require collaboratively maintaining and developing the critical packages and/or infrastructure. That would require getting everyone with any effort in SAS analysis software identified and together to discuss “infrastructure” support models.
	* Science is going to pretty pictures. Given advances in microscopy and crystallography, SAS software needs to produce 3D pictures more routinely or our community will becomes road kill		* Science is going to pretty pictures. Given advances in microscopy and crystallography, SAS software needs to produce 3D pictures more routinely or our community will becomes road kill
			** Arguably things are really moving to 4D, to provide the time dependent structure which will remain difficult by any other technique
	** Molecular Simulation by default gives such images - can we leverage the current interest in that software area?		** Molecular Simulation by default gives such images - can we leverage the current interest in that software area?
	** Deep Learning and even correlation analysis could also help this.		** Deep Learning and even correlation analysis could also help this.

Butler: /* Actions */

2019-07-11T18:38:13Z

Actions

← Older revision		Revision as of 18:38, 11 July 2019
Line 39:		Line 39:
	== Actions ==		== Actions ==

	* Video tutorials for selecting software program(s) - Assigned to: Dissemination Group		* Video tutorials for selecting software program(s) - '''Assigned to:''' ''Dissemination Group''
	* Smallangle.org: Separate out highly used software and mark supported vs unsupported - Assigned to: Dissemination Group		* Smallangle.org: Separate out highly used software and mark supported vs unsupported - '''Assigned to:''' ''Dissemination Group''
	* Software usage across different facilities - Assigned to: TBD		* Software usage across different facilities - '''Assigned to:''' ''TBD''

Butler: /* Actions */

2019-07-11T18:36:15Z

Actions

← Older revision		Revision as of 18:36, 11 July 2019
Line 39:		Line 39:
	== Actions ==		== Actions ==

	* Video tutorials for selecting software program(s) - Assigned to: ~~TBD~~		* Video tutorials for selecting software program(s) - Assigned to: Dissemination Group
	* Smallangle.org: Separate out highly used software and mark supported vs unsupported - Assigned to: ~~TBD~~		* Smallangle.org: Separate out highly used software and mark supported vs unsupported - Assigned to: Dissemination Group
	* Software usage across different facilities - Assigned to: TBD		* Software usage across different facilities - Assigned to: TBD

Butler: /* Summary */

2019-07-11T18:33:54Z

Summary

← Older revision		Revision as of 18:33, 11 July 2019
Line 19:		Line 19:
	** Youtube for users but also beamline scientists		** Youtube for users but also beamline scientists
	** Add citations and activity etc for each software package listed on the canSAS portal page could be a great help in making whats available more accessible		** Add citations and activity etc for each software package listed on the canSAS portal page could be a great help in making whats available more accessible
	** Would also be good if most highly used packages moved to top so people don't have to read through the entire list ~~always~~.		** Would also be good if most highly used packages moved to top so people don't have to always read through the entire list.
	* There is probably a need for special workflows for focused problems that give users the 2-3 parameters they are looking for.		* There is probably a need for special workflows for focused problems that give users the 2-3 parameters they are looking for.
	* If all packages are designed as scriptable first they can then more easily be pulled into various frameworks to develop different workflows for different communities for example or in frameworks for correlative/multi-modal analysis. We should try to encourage all package writers to do this. It is really the correct way to be writing software anyway.		* If all packages are designed as scriptable first they can then more easily be pulled into various frameworks to develop different workflows for different communities for example or in frameworks for correlative/multi-modal analysis. We should try to encourage all package writers to do this. It is really the correct way to be writing software anyway.
Line 34:		Line 34:
	* Networking grants a great idea and some effort since last canSAS but need grants to do actual work.		* Networking grants a great idea and some effort since last canSAS but need grants to do actual work.

			=== contemporaneous notes by Jeff Krzywon available here ===
	[https://docs.google.com/document/d/11IW87UsSOT9_eCTwgOd5Sn3GDbqH5zGzwdG31ZyPnUM/edit?usp=sharing Google Doc With Notes]		[https://docs.google.com/document/d/11IW87UsSOT9_eCTwgOd5Sn3GDbqH5zGzwdG31ZyPnUM/edit?usp=sharing Google Doc With Notes]

Butler: /* Session Notes */

2019-07-11T18:12:12Z

Session Notes

Butler: /* Session Notes */

2019-07-11T17:56:32Z

Session Notes

← Older revision		Revision as of 17:56, 11 July 2019
Line 11:		Line 11:
	* It seems that there are a number of packages that are being developed with similar plugin architectures in python		* It seems that there are a number of packages that are being developed with similar plugin architectures in python
	** A true monoculture is probably not healthy		** A true monoculture is probably not healthy
	But there does seem to be an insatiable and unstoppable need for everyone to re-invent the wheel. Question:** what drives that?		** But there does seem to be an insatiable and unstoppable need for everyone to re-invent the wheel. '''Question:''' what drives that?
	*** Desire to be able to respond to ones users in a timely fashion? --> collaborative software development?		*** Desire to be able to respond to ones users in a timely fashion? --> collaborative software development?
	*** Desire to get recognition by doing something believed to be better?
	*** Perhaps biggest may be lack of good understanding of what exists and/or how to collaborate on it?		*** Perhaps biggest may be lack of good understanding of what exists and/or how to collaborate on it?
			**** Even instrument scientists might not know which tool(s) to use. They might thus push tools that are known but may not be the best tool for the job
	* Dissemination should work on reaching instrument scientists and potential developers as well as users about what is already there		* Dissemination should work on reaching instrument scientists and potential developers as well as users about what is already there
	** Lots of “advertising needs”		** Lots of “advertising needs”

Butler: /* Session Notes */

2019-07-11T17:39:52Z

Session Notes

Butler: /* Session Notes */

2019-07-11T15:04:05Z

Session Notes

← Older revision		Revision as of 15:04, 11 July 2019
Line 7:		Line 7:

	== Session Notes ==		== Session Notes ==

	~~The session began with a presentation by Sven-Jannick Wöhnert on dpdak~~

	Highlights from the discussion include:		Highlights from the discussion include:
Line 20:		Line 18:
	** Lots of “advertising needs”		** Lots of “advertising needs”
	** Youtube for users but also beamline scientists		** Youtube for users but also beamline scientists
	** Add citations and activity etc for packages on canSAS portal page		** Add citations and activity etc for packages on canSAS portal page could be a great help in making whats available more accessible
	* ~~Scriptable~~ packages in ~~python gives first go at correlation~~		** Would also be good if most highly used packages moved to top so people don't have to read through the entire list always.
			* If all packages are designed as scriptable first they can then more easily be pulled into various frameworks to develop different workflows for different communities for example or, more importantly, in frameworks for correlative/multi-modal analysis
	* Securing funding for long term maintenance and funding		* Securing funding for long term maintenance and funding
	** Can we reposition analysis software as infrastructure. In ~~europe~~ there is an evolving new infrastructure funding model which would support infrastructure indefinitely (presumably as long as it is a useful infrastructure?)		** Can we reposition analysis software as infrastructure. In Europe there is an evolving new infrastructure funding model which would support infrastructure indefinitely (presumably as long as it is a useful infrastructure?)
	*** PANOSC and ???		*** PANOSC and ???
	** Alternatively Facilities presumably have a need for users to have adequate analysis software. Problem is prohibitive cost. So can we bring the costs into a realistic range?		** Alternatively Facilities presumably have a need for users to have adequate analysis software. Problem is prohibitive cost. So can we bring the costs into a realistic range?
	*** This would probably require collaboratively maintaining and developing the critical packages and/or infrastructure. That would require getting everyone with any effort in SAS analysis software identified and together to discuss “infrastructure” support models.		*** This would probably require collaboratively maintaining and developing the critical packages and/or infrastructure. That would require getting everyone with any effort in SAS analysis software identified and together to discuss “infrastructure” support models.
	* 3D pictures needed or our community becomes road kill		* 3D pictures needed or our community becomes road kill
	* ~~Use molecular simulation~~ and correlation analysis~~. ML~~ could also help		** Molecular Simulation by default gives such images - can we leverage the current interest in that software area?
	* ~~Get~~ packages to take “STEP ~~files”~~ and convert to scattering		** Deep Learning and even correlation analysis could also help this.
			We should just get all** packages to take appropriate image files (CAD? “STEP files?”) and convert to scattering
			*** NOTE added in general discussion: Brian Pauw is developing such a package. Can't yet handle contrast because the CAD file type does not support color. Could we use layering? Should co-ordinate with Brian to develop package further for general use.
	* Workflows for focused problems that give you the 3 parameters that you want		* Workflows for focused problems that give you the 3 parameters that you want
	* Networking grants a great idea and some effort since last canSAS but need grants to do actual work.		* Networking grants a great idea and some effort since last canSAS but need grants to do actual work.

Butler: /* Session Notes */

2019-07-11T14:52:26Z

Session Notes

← Older revision		Revision as of 14:52, 11 July 2019
Line 12:		Line 12:
	Highlights from the discussion include:		Highlights from the discussion include:
	* It seems that there are a number of packages that are being developed with similar plugin architectures in python		* It seems that there are a number of packages that are being developed with similar plugin architectures in python
	** ~~Noted that more than one~~ is ~~important~~		** A true monoculture is probably not healthy
	** But there does seem to be an insatiable and unstoppable need to re-invent the wheel ~~myself~~:		But there does seem to be an insatiable and unstoppable need for everyone to re-invent the wheel. Question:** what drives that?
	*** question is what drives that?		*** Desire to be able to respond to ones users in a timely fashion? --> collaborative software development?
	**** Need to ~~have access~~		*** Desire to get recognition by doing something believed to be better?
	**** Desire to ~~do "~~better~~" and get recognized~~?		*** Perhaps biggest may be lack of good understanding of what exists and/or how to collaborate on it?
	**** ~~Lack of "advertising" -~~ Dissemination should work on reaching instrument scientists and potential developers about what is already there		* Dissemination should work on reaching instrument scientists and potential developers as well as users about what is already there
	* Lots of “advertising needs”		** Lots of “advertising needs”
	* Youtube for users but also beamline scientists		** Youtube for users but also beamline scientists
	* Add citations and activity etc for packages on canSAS portal page		** Add citations and activity etc for packages on canSAS portal page
	* Being able to respond to ones users
	* Scriptable packages in python gives first go at correlation		* Scriptable packages in python gives first go at correlation
	* ~~Software~~ as ~~Infrastructure~~		* Securing funding for long term maintenance and funding
	** PANOSC and ~~OSC~~		** Can we reposition analysis software as infrastructure. In europe there is an evolving new infrastructure funding model which would support infrastructure indefinitely (presumably as long as it is a useful infrastructure?)
	* Facilities? ~~Would~~ require getting everyone with any effort in SAS analysis software identified and together to discuss “infrastructure” support models		*** PANOSC and ???
			** Alternatively Facilities presumably have a need for users to have adequate analysis software. Problem is prohibitive cost. So can we bring the costs into a realistic range?
			*** This would probably require collaboratively maintaining and developing the critical packages and/or infrastructure. That would require getting everyone with any effort in SAS analysis software identified and together to discuss “infrastructure” support models.
	* 3D pictures needed or our community becomes road kill		* 3D pictures needed or our community becomes road kill
	* Use molecular simulation and correlation analysis. ML could also help		* Use molecular simulation and correlation analysis. ML could also help

Butler: /* Discussion session on Software */

2019-07-11T14:28:32Z

Discussion session on Software

← Older revision		Revision as of 14:28, 11 July 2019
Line 2:		Line 2:
	Chair : Paul Butler		Chair : Paul Butler

	[[Media:canSAS_SoftwareDiscussion.pdf‎\|Water water everywhere, nor any drop to drink.]]		Session Plenary Overview : [[Media:canSAS_SoftwareDiscussion.pdf‎\|Water water everywhere, nor any drop to drink.]]

			Sven-Jannick Wöhnert : <<dpdak slides go here>>

	== Session Notes ==		== Session Notes ==

← Older revision		Revision as of 18:12, 11 July 2019
Line 8:		Line 8:
	== Session Notes ==		== Session Notes ==

	~~Highlights from the discussion include:~~		=== Summary ===
	* It seems that there are a number of packages that are being developed with similar plugin architectures in python		* It seems that there are a number of packages that are being developed with similar plugin architectures in python
	** A true monoculture is probably not healthy		** A true monoculture is probably not healthy
	** But ~~there does~~ seem to ~~be an insatiable and unstoppable need for everyone to~~ re-~~invent~~ the wheel. '''Question:''' what drives that?		** But we do seem to have a horrible history of re-inventing the wheel. '''Question:''' what drives that?
	*** Desire to be able to respond to ones users in a timely fashion? --> collaborative software development?		*** Could be support issues: Desire to be able to respond to ones users in a timely fashion? --> collaborative software development?
	*** Perhaps biggest may be lack of good understanding of what exists and/or how to collaborate on it?		*** Perhaps biggest issue may be lack of good understanding of what exists and/or how to collaborate on it?
	**** Even instrument scientists might not know which tool(s) to use. They might thus push tools that are known but may not be the best tool for the job		**** Even instrument scientists might not know which tool(s) to use. They might thus push tools that are known but may not be the best tool for the job
	* Dissemination should work on reaching instrument scientists and potential developers as well as users about what is already there		* Dissemination should work on reaching instrument scientists and potential developers as well as users about what is already there
	** Lots of ~~“advertising needs”~~		** Lots of video tutorials around but should link to them appropriately from portal
	** Youtube for users but also beamline scientists		** Youtube for users but also beamline scientists
	** Add citations and activity etc for ~~packages~~ on canSAS portal page could be a great help in making whats available more accessible		** Add citations and activity etc for each software package listed on the canSAS portal page could be a great help in making whats available more accessible
	** Would also be good if most highly used packages moved to top so people don't have to read through the entire list always.		** Would also be good if most highly used packages moved to top so people don't have to read through the entire list always.
	* There is probably a need for special workflows for focused problems that give users the 2-3 parameters they are looking for.		* There is probably a need for special workflows for focused problems that give users the 2-3 parameters they are looking for.
Line 30:		Line 30:
	** Molecular Simulation by default gives such images - can we leverage the current interest in that software area?		** Molecular Simulation by default gives such images - can we leverage the current interest in that software area?
	** Deep Learning and even correlation analysis could also help this.		** Deep Learning and even correlation analysis could also help this.
	We should just get all** packages to take appropriate image files (CAD? “STEP files?”) and convert to scattering		** We should just get '''all''' packages to take appropriate image files (CAD? “STEP files?”) and convert to scattering
	*** NOTE added in general discussion: Brian Pauw is developing such a package. Can't yet handle contrast because the CAD file type does not support color. Could we use layering? Should co-ordinate with Brian to develop package further for general use, robustness and maintenance.		*** NOTE added in general discussion: Brian Pauw is developing such a package. Can't yet handle contrast because the CAD file type does not support color. Could we use layering? Should co-ordinate with Brian to develop package further for general use, robustness and maintenance.
	* Networking grants a great idea and some effort since last canSAS but need grants to do actual work.		* Networking grants a great idea and some effort since last canSAS but need grants to do actual work.

← Older revision		Revision as of 17:39, 11 July 2019
Line 20:		Line 20:
	** Add citations and activity etc for packages on canSAS portal page could be a great help in making whats available more accessible		** Add citations and activity etc for packages on canSAS portal page could be a great help in making whats available more accessible
	** Would also be good if most highly used packages moved to top so people don't have to read through the entire list always.		** Would also be good if most highly used packages moved to top so people don't have to read through the entire list always.
	* If all packages are designed as scriptable first they can then more easily be pulled into various frameworks to develop different workflows for different communities for example or~~, more importantly,~~ in frameworks for correlative/multi-modal analysis		* There is probably a need for special workflows for focused problems that give users the 2-3 parameters they are looking for.
			* If all packages are designed as scriptable first they can then more easily be pulled into various frameworks to develop different workflows for different communities for example or in frameworks for correlative/multi-modal analysis. We should try to encourage all package writers to do this. It is really the correct way to be writing software anyway.
	* Securing funding for long term maintenance and funding		* Securing funding for long term maintenance and funding
	** Can we reposition analysis software as infrastructure. In Europe there is an evolving new infrastructure funding model which would support infrastructure indefinitely (presumably as long as it is a useful infrastructure?)		** Can we reposition analysis software as infrastructure. In Europe there is an evolving new infrastructure funding model which would support infrastructure indefinitely (presumably as long as it is a useful infrastructure?)
	*** PANOSC and ~~???~~		*** PANOSC and [https://www.eosc-portal.eu/ the European Open Science Cloud project, EOSC]
	** Alternatively Facilities presumably have a need for users to have adequate analysis software. Problem is prohibitive cost. So can we bring the costs into a realistic range?		** Alternatively Facilities presumably have a need for users to have adequate analysis software. Problem is prohibitive cost. So can we bring the costs into a realistic range?
	*** This would probably require collaboratively maintaining and developing the critical packages and/or infrastructure. That would require getting everyone with any effort in SAS analysis software identified and together to discuss “infrastructure” support models.		*** This would probably require collaboratively maintaining and developing the critical packages and/or infrastructure. That would require getting everyone with any effort in SAS analysis software identified and together to discuss “infrastructure” support models.
	* 3D pictures ~~needed~~ or our community becomes road kill		* Science is going to pretty pictures. Given advances in microscopy and crystallography, SAS software needs to produce 3D pictures more routinely or our community will becomes road kill
	** Molecular Simulation by default gives such images - can we leverage the current interest in that software area?		** Molecular Simulation by default gives such images - can we leverage the current interest in that software area?
	** Deep Learning and even correlation analysis could also help this.		** Deep Learning and even correlation analysis could also help this.
	We should just get all** packages to take appropriate image files (CAD? “STEP files?”) and convert to scattering		We should just get all** packages to take appropriate image files (CAD? “STEP files?”) and convert to scattering
	*** NOTE added in general discussion: Brian Pauw is developing such a package. Can't yet handle contrast because the CAD file type does not support color. Could we use layering? Should co-ordinate with Brian to develop package further for general use.		*** NOTE added in general discussion: Brian Pauw is developing such a package. Can't yet handle contrast because the CAD file type does not support color. Could we use layering? Should co-ordinate with Brian to develop package further for general use, robustness and maintenance.
	* Workflows for focused problems that give you the 3 parameters that you want
	* Networking grants a great idea and some effort since last canSAS but need grants to do actual work.		* Networking grants a great idea and some effort since last canSAS but need grants to do actual work.