07-01-2011 06:54 AM
dear friends!
Please, how can I read the attached file (test.txt) with LabVIEW 8.6. In the same VI, can I convert it into a real txt file with the results presented in rows and columns? Please, any idea? I need help!
Solved! Go to Solution.
07-01-2011 07:52 AM
How did that get the .txt extension?
That is obviously not supposed to be a plain text extension.
Without knowing the correct data type, it would be impossible very difficult to typecast that data.
07-01-2011 09:07 AM
Looking at the first few lines suggests its something to do with RELAP5 version 3.2...? In which case, these chaps are more likely to be some help.
07-01-2011 09:25 AM
@_Ian_ wrote:
Looking at the first few lines suggests its something to do with RELAP5 version 3.2...? In which case, these chaps are more likely to be some help.
Following up on Ian's idea, I don't think this is supposed to be a text file at all. It looks like this is some type of outputted plot, probably with some proprietary format that you need their software to open.
07-01-2011 09:34 AM
It could help if the honorable professor could tell us what kind application that did create it. Or did it just end up on your computer desktop 😉
07-01-2011 10:53 AM
In fact, the txt file is the result (output file - named restart plot file) of the RELAP5 code (Thermal Hydraulic Code). I would use this (restart plot file - test.rst) to develop a visual simulation of the temperatures calculated in LabVIEW using RGB with the results of the RELAP5 code. I'm sending the original compressed file (test.rst). Do you think the plot restart file is binary? Would read it in Labview to develop my application?
07-01-2011 10:55 AM
In fact, the txt file is the result (output file - named restart plot file) of the RELAP5 code (Thermal Hydraulic Code). I would use this (restart plot file - test.rst) to develop a visual simulation of the temperatures calculated in LabVIEW using RGB with the results of the RELAP5 code. I'm sending the original compressed file (test.rst). Do you think the plot restart file is binary? Would read it in Labview to develop my application?
07-01-2011 10:56 AM
In fact, the txt file is the result (output file - named restart plot file) of the RELAP5 code (Thermal Hydraulic Code). I would use this (restart plot file - test.rst) to develop a visual simulation of the temperatures calculated in LabVIEW using RGB with the results of the RELAP5 code. I'm sending the original compressed file (test.rst). Do you think the plot restart file is binary? Would read it in Labview to develop my application?
07-01-2011 01:10 PM
The plot restart file is binary.
Unfortunately, without a description of the actual file format from the RELAP developers, I don't think you're going to get very far on decoding the file.
You need to get in contact with the RELAP authors directly.
Here's the blurb from the RELAP manual:
3.1.4.2 The Restart-Plot File.
The restart-plot file contains virtually all calculation parameters
(pressures, temperatures, void fractions, flow rates, etc.) for the entire transient calculation.
A common misconception is that a parameter needs to be specified using a minor edit request in
order to be available in the restart-plot file when the calculation is complete. A minor edit request affects
only the printed output. The restart-plot file may be accessed repeatedly as new data needs arise. However,
during a calculation, data are written to the restart-plot file only at the minor edit (and plot point)
frequency. Once a calculation has been performed, it is not possible to recover the data between the data
points written to the restart-plot file. Therefore, it is important to select a minor edit (and plot point)
frequency that will provide plot points at an interval appropriate for the problem being solved. In practice,
the minor edit (and plot point) frequency should be changed during the calculation as the problem proceeds
from one phase to the next. Frequent points should be selected during the problem phases where rapid
RELAP5-3D/2.4
INEEL-EXT-98-00834-V5 3-18
changes in parameters are expected. For economy, less frequent points should be selected during phases
where quiescent conditions are expected.
Calculations typically are accomplished using multiple restarts. (See Volume II for restart input
requirements.) For example, a new problem is run from 0 to 10 seconds. This early portion is analyzed and
rerun from time zero as errors are corrected. When a successful calculation to 10 seconds has been made, a
restart run is made (e.g., from 10 to 30 seconds), and so on. RELAP5-3D
© provides the flexibility to
change virtually any feature of the model at any restart point. When model changes are incorporated on
restart, the restart-plot file reflects those changes only after the point in the calculation where they were
implemented. In the above example, if an injection system is added to the model at 10 seconds, then data
for the added components exists only for times after 10 seconds. Model additions, deletions, and changes
are permanently implemented. If a model change is made at 10 seconds, the revised model remains in
effect unless further modifications are made at subsequent restart points.
When a calculation has been completed, the restart-plot file becomes a valuable record of the
calculation. If lost, replacing it would require reperforming the calculation, generally at considerable
expense. At any later date, the file may be accessed and previously unaccessed data may be obtained as
needed to extend analysis. Therefore, it is recommended that the restart-plot files of important calculations
be protected securely and permanently.