Skip to content

Commit 4d6fd35

Browse files
committed
Added architecture FAQ
1 parent 25c20df commit 4d6fd35

1 file changed

Lines changed: 10 additions & 3 deletions

File tree

docs/userguides/scholar/scholar-spark.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,11 @@ authors:
66
date:
77
created: 2026-06-11
88
updated: 2026-06-11
9-
search:
10-
exclude: true
119
resource: Scholar
1210
host: scholar.rcac.purdue.edu
1311
search:
1412
boost: 2
13+
exclude: true
1514
---
1615

1716
# Scholar Spark Nodes
@@ -324,10 +323,18 @@ module load modtree/spark
324323

325324
If you have built or downloaded your own applications, please rebuild any applications on a Spark node, or check for an `aarch64` distribution of your software.
326325

326+
### How can I check the architecture of the node I'm running on?
327+
328+
Since Scholar has nodes with `x86_64` architecture and `aarch64` architecture, you can use the following command to print the architecture of the node you are currently running on.
329+
330+
```bash linenums="0"
331+
uname -m
332+
```
333+
327334

328335
### How can I separate my `x86_64` applications from `aarch64` applications?
329336

330-
If you plan on working on both `aarch64` and `x86_64` nodes, we strongly reccomend separating applications and configurations in separate directories.
337+
If you plan on working on both `aarch64` and `x86_64` nodes, we strongly recommend separating applications and configurations in separate directories.
331338

332339
For example, you may choose to make separate `bin` directories for `x86_64` and `aarch64` applications. In your `~/.bash_profile` file, you can then source the correct applications based on the architecture:
333340

0 commit comments

Comments
 (0)