[easybuild] CrayIntel Compiler Chain and "intel" module

2016-06-02 Thread Andy Turner
(Renaming the thread as the discussion has moved on) Hi Guilherme, Thanks for responding on this and I think your suggestion is a good one and encodes the Intel version in the correct place. My other thought had been to remove the specification of the 'intel' module altogether from the

Re: [easybuild] Newbie question: Generic easyblock to use for VASP

2016-06-02 Thread Peretti-Pezzi Guilherme
Andy, The only way of ensuring reproducibility is to pin the intel version, and that was our focus when designing these toolchains, rather than having generic/versionless build recipes that might work or not depending on the defaults of your system. Since the intel version can be different from

Re: [easybuild] eb --job

2016-06-02 Thread Kenneth Hoste
On 02/06/16 04:59, Riccardo Murri wrote: Hi Gizo, thanks for the suggestion! However torque has a feature not to immediately remove a completed job from memory, but keep it for some configurable amount of time so that the qstat command can display its utilization, including an exit status.

Re: [easybuild] eb --job

2016-06-02 Thread Riccardo Murri
Hi Gizo, thanks for the suggestion! > However torque has a feature not to immediately remove a completed job from > memory, but keep it for some configurable amount of time so that the qstat > command can display its utilization, including an exit status. This feature > is not a default in