Consolidating them in that way could reduce code duplication and inconsistencies (e.g., like using hard-coded Matlab path in `qmatjob_array` and the user's default version in `qmatjob_loop`).

…

On Sat, Oct 21, 2017 at 5:49 PM, kupiqu ***@***.***> wrote: I see -- Enviat des del telèfon On Oct 21, 2017 17:23, "Jason Sherfey" ***@***.***> wrote: > Consolidation would mean combining all the submission scripts into one > file (including qmatjob_array, qmatjob_array_one_file, qmatjob_loop, > qmatjobs_memlimit_loop, and the new Octave-compatible versions). This > might be possible using additional arguments to direct the single > submission script based on 'qsub_mode' and 'one_solve_file_flag' in > dsCreateBatch and whether using Matlab or Octave. > > — > You are receiving this because you were assigned. > Reply to this email directly, view it on GitHub > <#249 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ ADshfKOJv3cFdG8QFMKK17vyha3limadks5sumDhgaJpZM4QBsxv> > . > — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#249 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB8qCejZGlng5HgrLBwCLFm6kt0bu6b3ks5sumbmgaJpZM4QBsxv> .

rename qmatjobs_* files to qjobs_* and make them work both in matlab and octave #249

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions