Level 3 processing doesn't pay attention to strun --output_dir param about jwst HOT 3 CLOSED

Just as an example of use with the association product names:

with open('the_association', 'r') as asn_fh:
    asn = Association.load(asn_fh)
my_result_model = code_returning_some_jwst_datamodels_result_model(asn)
output_dir = '/the/output/directory/path/from--output_dir'
product_type = 'i2d' # Assuming CALIMAGE3
product_name = asn['products'][0]['name']
full_output_path = output_dir + '/' + product_name.format(product_type=product_type)
my_result_model.save(full_output_path)

from jwst.

Regarding line 4 in the above example, if the user specifies the --output_dir param to strun, it will show up as an attribute of the pipeline or step that's being run, as self.output_dir. Hence pipeline modules can check for "self.output_dir is not None" and if so, then be sure to prepend the value of self.output_dir to the output file name.

from jwst.

Oh, and instead of using the direct approach of appending the path and filename just by using the "+" operator, it might be safer and more OS-benign to use the os.path.join function to do that, i.e. full_output_path = os.path.join(output_dir, product_name).

from jwst.