llnl / llnl/EQ3_6

Error - (EQLIB/indath) Have wrong file header "ckup "

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
20
Forks
1
PR merge metrics
No merged PRs in 30d

Description

(base) [hy38185@master eq3_6]$ ls
data1 input input.3ib input.3o input.6ib input.6o

(base) [hy38185@master eq3_6]$ /vol01/homes/hy38185/Software/eq3_6/bin/eq3nr data1 input

EQ3/6, Version 8.0a (EQ3/6-V8-REL-V8.0a-PC)
EQ3NR Speciation-Solubility Code (EQ3/6-V8-EQ3NR-EXE-R43a-PC)
Supported by the following EQ3/6 libraries:
EQLIB (EQ3/6-V8-EQLIB-LIB-R43a-PC)
EQLIBG (EQ3/6-V8-EQLIBG-LIB-R43a-PC)
EQLIBU (EQ3/6-V8-EQLIBU-LIB-R43a-PC)

Copyright (c) 1987, 1990-1993, 1995, 1997, 2002 The Regents of the
University of California, Lawrence Livermore National Laboratory.
All rights reserved.

This work is subject to additional statements and
disclaimers which may be found in the README.txt file
included in the EQ3/6 software transmittal package.

Run 22:57:24 21Mar2024

Reading the data1 file header section ...

* Error - (EQLIB/indath) Have wrong file header "ckup "
on the data1 file. The first five characters must be "data1".

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported `eq3nr data1 input` command and inspect the `data1` file header, which is reported as `ckup ` rather than `data1`. Determine whether the input file or the program is responsible; done means the command accepts the intended header or reports a clearly actionable input error.

Written by the indexing model from the issue text.

Assessment

Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.