lib/coderunner/instance_methods.rb in coderunner-0.17.5 vs lib/coderunner/instance_methods.rb in coderunner-0.17.6

- old
+ new

@@ -370,11 +370,11 @@ # Create, set up and check the validity of the custom class which deals with a particular simulation code. This class will be defined in a custom module in the folder <tt>code_modules/code_name</tt>, where <tt>'code_name'</tt> is the name of the code. The only option is <tt>modlet:</tt>. # # If the custom class has already been set up, this method just returns the class. - def self.setup_run_class(code, options={}) + def self.setup_run_class(code, options={}) # logf(:setup_code) # log(:code, code) modlet = options[:modlet] version = options[:version] @@ -469,10 +469,10 @@ # logi("run_class.variables[0] in setup_code", run_class.variables[0]) # ep 'finished' return run_class - end + end # Traverse the directory tree below the root folder, detecting and analysing all runs within that folder. Although runs submitted by CodeRunner will all be in one folder in the root folder, it is not necessary for the runs to be organised like that. This is because CodeRunner can also be used to analyse runs which it did not submit. # # All subfolders of the root_folder will be analysed, except for ones specified in the run class property <tt>excluded_sub_folders</tt>, or those containing the hidden file '.CODE_RUNNER_IGNORE_THIS_DIRECTORY'