Differences

This shows you the differences between two versions of the page.

--- include_and_ingest [2024/07/19 11:19] – johnsoevans
+++ include_and_ingest [2024/07/20 06:32] (current) – johnsoevans
@@ Line 6: / Line 6: @@
 <code topas>#ingest FILE_NAME</code>
-"#ingest FILE_NAME" is similar, but puts the information in teh external file directly into the INP file.  The information and refined values then get written to the OUT file, and can be analysed or used in subsequent refinements.
+"#ingest FILE_NAME" is similar, but puts the information in the external file directly into the INP file.  The information and refined values then get written to the OUT file, and can be analysed or used in subsequent refinements.  Thanks to Peter Khalifah for the idea.
-The FILE_NAME can also be a macro name so macros get explicitly written to the INP. The macro itself can come from the following sources:
+The FILE_NAME can also be a macro name. The macro itself can come from the following sources:
   * From TOPAS.INC
-  * From the command line, for example: tc test_examples\ingest-1.inp “macro File_Name_Macro {  ingest-2.inc } “
+  * From the command line, for example type: tc ingest-1.inp “macro Name_Of_Macro {  FILE_NAME_CONTAINING_INPTEXT.inc } “
-  * From a #include file included at the command line, for example: tc test_examples\ingest-1.inp “#include SOME_INCLUDE_FILE “
+  * From a #include file included at the command line, for example: tc ingest-1.inp “#include SOME_INCLUDE_FILE “
 Any macro defined in SOME_INCLUDE_FILE can be used as a FILE_NAME for #ingest.
@@ Line 27: / Line 27: @@
 The above means that #ingest can be used with num_rums etc.
+Examples will be in test_examples\ingest\.