Skip to content

Allow unique scan path specification for multi-layer builds#46

Closed
kincaidkc wants to merge 1 commit into
mainfrom
khk/diff-scan-paths
Closed

Allow unique scan path specification for multi-layer builds#46
kincaidkc wants to merge 1 commit into
mainfrom
khk/diff-scan-paths

Conversation

@kincaidkc

Copy link
Copy Markdown
Collaborator

This PR modifies the multi-layer utility to require a list of scan paths associated with each heat source and build layer. The first line of the scan path list file should contain the name of each heat source, while subsequent lines should contain the name of the scan path file to use for each heat source for each layer. For example, the scan path list for a case with 3 heat sources and 4 layers might look like:

beam_1_name beam_2_name beam_3_name
path_11 path_21 path_31
path_12 path_22 path_32
path_13 path_23 path_33
path_14 path_24 path_34

The scan path list file is specified using the -scanPathList <list_file> flag in the runLayers utility.

The multiLayerPBF tutorial is modified to use this functionality to achieve a back-and-forth scan pattern.

Important note: These modifications assume that the time for each layer is constant, and equal to the end time specified in the controlDict of the base case file.

…ifferent scan path files for each heat source/layer
@kincaidkc kincaidkc self-assigned this Mar 21, 2025
@kincaidkc kincaidkc requested review from colemanjs and streeve March 21, 2025 16:37
@colemanjs

Copy link
Copy Markdown
Collaborator

@kincaidkc, I believe that this functionality is handled properly now from #66. Can you confirm?

@kincaidkc

Copy link
Copy Markdown
Collaborator Author

@kincaidkc, I believe that this functionality is handled properly now from #66. Can you confirm?

Right, let's close this.

@kincaidkc kincaidkc closed this Sep 18, 2025
@colemanjs colemanjs deleted the khk/diff-scan-paths branch October 13, 2025 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants