From 5021b6e0b195b429f59847be42a883a3f7332186 Mon Sep 17 00:00:00 2001
From: a1120960 <77258073+a1120960@users.noreply.github.com>
Date: Tue, 23 Jul 2024 10:29:04 +0930
Subject: [PATCH] updated README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 3cafa14..82b5b8f 100644
--- a/README.md
+++ b/README.md
@@ -63,7 +63,7 @@ For citation purposes, please reference our arXiv paper (UPCOMING):
 - Any help or advice on how to make these plots and/or data more accessible will be much appreciated. 
 
 # FUTURE
-- I would like to extend **SWaP** to include other significant barriers to deployability. As an example **SWaP-PC** would add:
+- I would like to extend **SWaP** to include other significant barriers to deployability. Ideally these would be something that can be easily captured as a value, so that it can be multiplied by the SWaP number. As an example **SWaP-PC** would add:
     - **Personnel**: How many people are required to run the system? For many of the modern portable systems this would be a minimum of a single person to turn the key or press a button, and begin operation. On the other hand some research clocks may need an entire team of people to set up and run the clock. 
     - **Cost**: How much does the system cost? For research clocks this may be hard, if not impossible to determine, or might not want to be revealed.
 - Another factor to explore could be device manufacturability, especially at scale. Very difficult to assign a value to this, however.