← Back to Recording

Summary

Overview

This course segment demonstrates the configuration of a data processing workflow in a visual automation tool (likely OpenEye or similar), focusing on variable creation, file input/output operations, and output format validation. The trainer guides participants through setting a string variable to hold file content, naming and directing an output file to avoid path complexity, and verifying the output format for compatibility with downstream systems. The session concludes with troubleshooting and remote screen-sharing to resolve visibility and execution issues.

Topic (Timeline)

1. Variable Configuration and File Content Assignment [00:00:01.600 - 00:01:13.600]

  • The trainer finalizes the setup of a string variable named “Prom” to hold the content of an input file.
  • Demonstrates assigning file content to the variable, emphasizing that the data will be processed as a string.
  • Notes visibility limitations due to a small laptop screen, affecting real-time observation of participant actions.

2. Output File Configuration and Naming Strategy [00:01:13.600 - 00:02:47.440]

  • Configures the tefile output component to write the processed data to a file.
  • Avoids using full file paths by referencing an existing file (Prom) in the OpenEye/temp directory and renaming it to Prom_Underexcord to ensure clarity and portability.
  • Explains the rationale: preventing reliance on absolute paths (e.g., “last temporal” or “last” directories) to improve workflow portability and reduce errors.

3. Workflow Trigger and Component Connection [00:02:47.440 - 00:04:04.090]

  • Connects the teyabarrow component as a trigger to a subjob, establishing the sequence:
    1. Variable creation
    2. Assignment of file content to the variable
    3. Generation of output file via the configured tefile output
  • Confirms the final teyabarrow structure matches a previously shared template.
  • Emphasizes the need to validate the output file format for compatibility with OpenEye.

4. Execution and Output Validation [00:04:04.090 - 00:05:23.990]

  • Executes the workflow, noting occasional issues with the tool running the previous job instead of the current one.
  • Verifies the output file (Prom_Underexcord) in the designated OpenEye directory.
  • Confirms the file is generated in the expected format, but observes that date fields appear concatenated without clear delimiters.
  • Notes that whitespace is present and will be correctly interpreted by the system.
  • Advises participants to check for errors and report them for remote troubleshooting.

5. Remote Troubleshooting and Screen Access [00:05:23.990 - 00:06:20.010]

  • Trainer attempts to access a participant’s screen (Raúl) to diagnose visibility issues caused by single-monitor limitations.
  • Unable to establish remote connection, but proceeds to review their own configuration.
  • Confirms that Raúl’s Prom variable points to the corrected file in the OpenEye directory, aligning with the demonstrated workflow.

Appendix

Key Principles

  • Use relative file references and rename output files to avoid hardcoding paths.
  • Validate output format early to ensure compatibility with downstream systems (e.g., OpenEye).
  • Isolate variable assignment and file output as distinct, sequential steps in the workflow.

Tools Used

  • OpenEye (platform/environment)
  • tefile output component
  • teyabarrow trigger component
  • String variable for file content handling

Common Pitfalls

  • Tool executing the previous job instead of the current one during run.
  • Inability to verify output due to limited screen real estate or single-monitor setup.
  • Misunderstanding of file path references leading to incorrect output locations.

Practice Suggestions

  • Always test output file format manually after execution.
  • Use consistent, descriptive naming for variables and output files (e.g., Prom_Underexcord).
  • When sharing workflows, provide template configurations to reduce setup errors.