Peter Willendrup

McStas 2018 Survey Feedback 6: saved config, user contributions.

1

Saved configurations in the windows gui don't seem to be well handled. A revised user contributed component and instrument repository would be nice.

McStas 2018 Survey Feedback 7: documentation

1

Better documentation on the various components and what their limitations are, what particular geometry they like etc

McStas 2018 Survey Feedback 8: use of HPC clusters

1

A feature that could be very useful for queued runs in cluster environments with privileges, is the possibility of pausing a run, recording the current state, in case another user...

McStas 2018 Survey Feedback 9: process for validation of components

2

It is important to have validated components to improve confidence in the silumations. I found bugs in some components and material files.

McStas 2018 Survey Feedback 10: models for many instruments in facilities

1

I would like a concerted move wth the neutron facilities to provide verified instrument files for all public instruments, which could then be used for basic neutron training with confirable...

More robust WHEN statement built in/example generators for compound components (e.g. guides or detector arrays) More flexible include statements

McStas 2018 Survey Feedback 3: Multiple scattering in powder

3

Multiple scattering in powder sample :-)

SASmodels - better solution for namespaces around the individual c-codes

8

In a recent discussion on mcstas-users (https://mailman2.mcstas.org/pipermail/mcstas-users/2019q3/001301.html) it looks relevant to be able to combine more than one sasmodel in the same instrument. I propose that we make an alternative...

mcrun: Find a way to specify e.g. Monitor_nD options="..." strings that don't clash with other instr parms

2

Some sort of "comment" identifier maybe? Would also mean that e.g. "something, something else" is not interpreted as a scan clearly post 2.4 - and should go in mccode_utils