5.2 beta branch

[lizadams]

Note, currently there are two files that are pulled down from the EPA github repository that are in a weird state. "Changes not staged for commit"
modified: UTIL/create_ebi/src_RXNSU/junit.F
modified: UTIL/inline_phot_preproc/src/CSQY_DATA.F

• resolve the status of these files, as it is confusing to users

Commands used are listed below:

git clone -b 5.2Beta https://github.com/USEPA/CMAQ

Cloning into 'CMAQ'...
remote: Counting objects: 23880, done.
remote: Total 23880 (delta 0), reused 0 (delta 0), pack-reused 23880
Receiving objects: 100% (23880/23880), 26.96 MiB | 10.06 MiB/s, done.
Resolving deltas: 100% (16062/16062), done.
Checking out files: 100% (2005/2005), done.

ls

CMAQ

cd CMAQ
ls

CCTM		POST		PREP		README.md	UTIL		config.cmaq

git status

On branch 5.2Beta
Your branch is up-to-date with 'origin/5.2Beta'.
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   UTIL/create_ebi/src_RXNSU/junit.F
	modified:   UTIL/inline_phot_preproc/src/CSQY_DATA.F

no changes added to commit (use "git add" and/or "git commit -a")

[lizadams]

config.cmaq has a path for /bin/uname that doesn't work on my mac. Can we remove the path and just use uname? Made an additional change as the uname -i command didn't work on my mac.

• Made this change and committed to repository: [5.2Beta 77f9861]

Did you check if the uname change had any impact on Linux systems? These scripts are primarily for supporting CMAQ on Linux. The -i flag is a key flag that is used to build the string for naming the executable (tells us whether the system is 32 or 64 bit). Did you replace with uname -m?

[lizadams]

• This is what I am seeing using the uname -m command on my mac:
  uname -m
  x86_64
  I will switch it to that, if it also works on linux machines.