Q10 - Revision history

Mcassdtm: /* Summary */

2014-11-06T16:28:48Z

‎Summary

Mcassdtm at 16:28, 6 November 2014

2014-11-06T16:28:34Z

Mcassdtm at 09:21, 6 November 2014

2014-11-06T09:21:26Z

Mcassdtm: /* Any other comments? */

2014-11-06T09:12:05Z

‎Any other comments?

Mcassdtm: Created page with "===Any other comments?==="

2014-11-05T11:27:53Z

Created page with "===Any other comments?==="

New page

===Any other comments?===

@@ Line 19: / Line 19: @@
 ====Summary====
 #Code development/maintenance in various guises
-#Training in using variuos packages is required
+#Training in using various packages is required

@@ Line 1: / Line 1: @@
 ===Any other comments?===
 #Would be nice if there was an obvious preferred open source tomographic reconstruction code that we (STFC/EPSRC) could recommend to users and modify ourselves for our own needs. If there are candidates here, maybe publicise the options more widely?
 #Would be nice to have somebody looking into maintenance and support of useful tools and software.
@@ Line 18: / Line 19: @@
 ====Summary====
 #Code development/maintenance in various guises
-#Training
+#Training in using variuos packages is required

← Older revision		Revision as of 09:21, 6 November 2014
Line 14:		Line 14:
	#I'm not sure if Diamond are as involved as they could be. If they are it certainly isn't communicated well to Users.		#I'm not sure if Diamond are as involved as they could be. If they are it certainly isn't communicated well to Users.
	#Many of the packages are great for visualization but quick mathematics (e.g. subtract two 3d data sets) requires recoding.		#Many of the packages are great for visualization but quick mathematics (e.g. subtract two 3d data sets) requires recoding.
		+
		+
		+	====Summary====
		+	#Code development/maintenance in various guises
		+	#Training

← Older revision		Revision as of 09:12, 6 November 2014
Line 1:		Line 1:
	===Any other comments?===		===Any other comments?===
		+
		+	#Would be nice if there was an obvious preferred open source tomographic reconstruction code that we (STFC/EPSRC) could recommend to users and modify ourselves for our own needs. If there are candidates here, maybe publicise the options more widely?
		+	#Would be nice to have somebody looking into maintenance and support of useful tools and software.
		+	#Visualisation and application of calibrations to data go hand-in-hand together, thus the greatest visualisation tool won't be used much if it isn't integrated into a data handling flow. A good example is XCrysDen, which makes all the difference between just number crunching with wien2k and actually seeing what you're doing.
		+	#It would be great if the visulisation tool developers would start to collaborate to develop libraries, data formats etc that could be shared between them, to speed up the development of new tools and functionality, and allow users access to the full spectrum of tools they require.
		+	#I'm happy to get involved with this CCP/project or any initiative it might lead on with. I'm passionate about data visualisation and have experience in developing such tools.
		+	#Training on visualisation tools are really lacking. There should be more of them.
		+	#More seminars to introduce what is available
		+	#There is a strong need for web-based visualization methods to integrate into web-based applications we are developing.
		+	#License sharing and advanced usage training
		+	#Lack of tools limits the science we are able to achieve.
		+	#Final note - Martin Turner at RAL is brilliant at cross promotion (between communities) and compiling enthusiastic newsletters and should be thoughtfully priased for his dedication to the subject. He and his team are successfully promoting they ideas that other communities are way ahead in.
		+	#I'm not sure if Diamond are as involved as they could be. If they are it certainly isn't communicated well to Users.
		+	#Many of the packages are great for visualization but quick mathematics (e.g. subtract two 3d data sets) requires recoding.