[CS2113-W13-2] FitTrack #22

TheDinos · 2024-09-25T02:56:06Z

FitTrack is a desktop application designed to assist students in training for the National Physical Fitness Award (NAPFA) test. It focuses on streamlining data entry through a Command Line Interface (CLI) for students who seek efficiency and focus.

Kobot7 · 2024-10-22T09:14:32Z

src/main/java/fittrack/calculator/Calculator.java

+                }
+            }
+            return 0; // return 0 points as performance is below the minimum standard
+        } catch (InvalidAgeException e) {


Is the variable name "e" informative enough?

Kobot7 · 2024-10-22T09:14:58Z

src/main/java/fittrack/calculator/Calculator.java

+    // Utility method to add age sub-table for a specific gender
+    protected static void addAgeSubTable(Map<LookUpKey, TreeMap<Integer, Integer>> pointsTable,
+                                         Gender gender, int age, int[][] points, boolean reverseOrder) {
+        assert age >= 12 && age <= 24 : "Age should be within 12 and 24 during table initialisation"; //


Accidental empty comment?

Kobot7 · 2024-10-22T09:16:09Z

src/main/java/fittrack/FitTrack.java

+
+        // Until the exit command is entered, execute command then read user input
+        while (!input.equals(EXIT_COMMAND)) {
+            assert !input.trim().isEmpty() : "User input should not be null or empty";


Is this supposed to be an assertion or exception?

Kobot7 · 2024-10-22T09:17:13Z

src/main/java/fittrack/calculator/Calculator.java

+        TreeMap<Integer, Integer> ageSubTable;
+        if (reverseOrder){
+            ageSubTable = new TreeMap<>(Comparator.reverseOrder());
+        } else{


Java reserved words should be followed by a white space

Kobot7 · 2024-10-22T09:17:52Z

src/main/java/fittrack/calculator/PullUpCalculator.java

+    private static final Map<LookUpKey, TreeMap<Integer, Integer>> pullUpTable = new HashMap<>();
+    private static final boolean reverseOrder = true;


Constant names must be all uppercase using underscore to separate words

Kobot7 · 2024-10-22T09:20:42Z

src/main/java/fittrack/exercisestation/PullUpStation.java

+    @Override
+    public String getName() {
+        return name;
+    }


If implementation of getName() is the same for every child class, you may consider implementing it in the parent class instead

Kobot7 · 2024-10-22T09:25:58Z

src/main/java/fittrack/storage/Storage.java

+    public static final String SAVE_FILE = "data/saveFile.txt"; // Path to the save file
+    public static final File SAVEFILE = new File(SAVE_FILE); // File object for the save file


Consider using more meaningful variable names, SAVE_FILE and SAVEFILE does not provide much context as to what differentiates them, leading to confusion when using it in the code

Kobot7 · 2024-10-22T09:27:38Z

src/main/java/fittrack/storage/Storage.java

+        // Assert that the session list is not null before loading
+        assert sessionList != null : "Session list must not be null";
+
+        Scanner s = new Scanner(SAVEFILE); // Create a Scanner to read the save file


Use more informative variable names

Kobot7 · 2024-10-22T09:49:11Z

src/main/java/fittrack/parser/Parser.java

+    public static void parse(User user, String input, ArrayList<TrainingSession> sessionList) {
+        assert input != null : "Input must not be null";
+        assert user != null : "User object must not be null";
+        assert sessionList != null : "Session list must not be null";
+
+        String[] sentence = {input, input};
+        String command = input;
+        String description = "";
+
+        // Split the input into command and description if applicable
+        if (input.contains(" ")) {
+            sentence = input.split(" ", 2);
+            command = sentence[0];
+            description = sentence[1];
+        }
+
+        switch (command) {
+        case SET_USER_COMMAND:
+            assert description.contains(" ") : "Invalid user data format";
+            sentence = description.split(" ", 2);
+            user.setGender(sentence[0]);
+            user.setAge(sentence[1]);
+            break;
+        case ADD_SESSION_COMMAND:
+            assert !description.isEmpty() : "Session description must not be empty";
+            LocalDateTime currentTime = LocalDateTime.now();
+            sessionList.add(new TrainingSession(currentTime, description, user));
+            printAddedSession(sessionList);
+            break;
+        case EDIT_EXERCISE_COMMAND:
+            sentence = description.split(" ", 3);
+            assert sentence.length == 3 : "Edit exercise command requires exactly 3 arguments";
+            int sessionIndex = Integer.parseInt(sentence[0]) - 1;
+            int exerciseIndex = Integer.parseInt(sentence[1]);
+            String exerciseData = sentence[2];
+            assert sessionIndex >= 0 && sessionIndex < sessionList.size() : "Session index out of bounds";
+            sessionList.get(sessionIndex).editExercise(exerciseIndex, exerciseData);
+            break;
+        case LIST_SESSIONS_COMMAND:
+            printSessionList(sessionList); // Print the list of sessions
+            break;
+        case VIEW_SESSION_COMMAND:
+            int viewIndex = Integer.parseInt(description) - 1;
+            assert viewIndex >= 0 && viewIndex < sessionList.size() : "View session index out of bounds";
+            printSessionView(sessionList, viewIndex); // Print the session view
+            break;
+        case DELETE_SESSION_COMMAND:
+            int indexToDelete = Integer.parseInt(description) - 1;
+            assert indexToDelete >= 0 && indexToDelete < sessionList.size() : "Delete session index out of bounds";
+            TrainingSession sessionToDelete = sessionList.get(indexToDelete);
+            sessionList.remove(indexToDelete);
+            printDeletedSession(sessionList, sessionToDelete);
+            break;
+        default:
+            printUnrecognizedInputMessage(); // Response to unrecognized inputs
+            break;
+        }
+    }


Try to avoid long methods. Perhaps consider extracting out the commands into separate methods

Kobot7 · 2024-10-26T11:18:16Z

src/main/java/fittrack/parser/Parser.java

+                System.out.println(e.getMessage());
+            }
+            printSessionView(sessionList, sessionIndex);
+            break;
+        case LIST_SESSIONS_COMMAND:
+            printSessionList(sessionList); // Print the list of sessions
+            break;
+        case VIEW_SESSION_COMMAND:
+            int viewIndex = Integer.parseInt(description) - 1;
+            assert viewIndex >= 0 && viewIndex < sessionList.size() : "View session index out of bounds";
+            printSessionView(sessionList, viewIndex); // Print the session view
+            break;
+        case DELETE_SESSION_COMMAND:
+            int indexToDelete = Integer.parseInt(description) - 1;
+            assert indexToDelete >= 0 && indexToDelete < sessionList.size() : "Delete session index out of bounds";
+            TrainingSession sessionToDelete = sessionList.get(indexToDelete);
+            sessionList.remove(indexToDelete);
+            printDeletedSession(sessionList, sessionToDelete);
+            break;
+        case ADD_REMINDER_COMMAND:
+            sentence = description.split(" ", 2);
+
+            String inputDeadline = sentence[1];
+            description = sentence[0];
+
+            assert !description.isEmpty() : "Reminder description must not be empty";
+            assert !Objects.equals(inputDeadline, "") : "Reminder deadline must not be empty";
+            LocalDateTime deadline = parseReminderDeadline(inputDeadline);
+            reminderList.add(new Reminder(description, deadline, user));
+            printAddedReminder(reminderList);
+            break;
+        case DELETE_REMINDER_COMMAND:
+            int reminderIndexToDelete = Integer.parseInt(description) - 1;
+            assert reminderIndexToDelete >= 0 && reminderIndexToDelete < reminderList.size() : "Delete reminder index "
+                    + "out of bounds";
+            Reminder reminderToDelete = reminderList.get(reminderIndexToDelete);
+            reminderList.remove(reminderIndexToDelete);
+            printDeletedReminder(reminderList, reminderToDelete);
+            break;
+        case LIST_REMINDER_COMMAND:
+            printReminderList(reminderList);
+            break;
+        case LIST_UPCOMING_REMINDER_COMMAND:
+            beginSegment();
+            printUpcomingReminders(reminderList);
+            break;
+
+        case "add-goal":  // use "add-goal" consistently in input and command handling
+            if (!description.isEmpty()) {
+                String[] goalParts = description.split(" ", 2);
+                String goalDescription = goalParts[0];
+                LocalDateTime goalDeadline = null;
+
+                if (goalParts.length > 1) {
+                    String goalDeadlineInput = goalParts[1];
+                    try {
+                        goalDeadline = parseGoalDeadline(goalDeadlineInput);
+                    } catch (IllegalArgumentException e) {
+                        System.out.println("Invalid date format: " + e.getMessage());
+                        return;
+                    }
+                }
+                Goal newGoal = new Goal(goalDescription, goalDeadline);
+                goalList.add(newGoal);
+                printAddedGoal(goalList);
+            } else {
+                System.out.println("Please specify a goal to add.");
+            }
+            break;
+
+        case "delete-goal":
+            try {
+                int index = Integer.parseInt(description) - 1;
+                if (index >= 0 && index < goalList.size()) {
+                    goalList.remove(index);
+                    System.out.println("Goal at index " + (index + 1) + " has been removed.");
+                } else {
+                    System.out.println("Invalid goal index.");
+                }
+            } catch (NumberFormatException e) {
+                System.out.println("Please specify a valid index to delete.");
+            }
+            break;
+
+        case "list-goal":
+            if (goalList.isEmpty()) {
+                System.out.println("No goals to display.");
+            } else {
+                System.out.println("Goals:");
+                for (int i = 0; i < goalList.size(); i++) {
+                    System.out.println((i + 1) + ". " + goalList.get(i));
+                }
+            }
+            break;
+
+        default:
+            printUnrecognizedInputMessage(); // Response to unrecognized inputs
+            break;
+        }
+    }


Method is too long. Do consider extracting out code for each command to a separate method

Kobot7 · 2024-10-26T11:19:13Z

src/main/java/fittrack/parser/Parser.java

+     *
+     * @param inputDeadline A string input by the user. Intended format is DD/MM/YYYY or DD/MM/YYYY HH:mm:ss.
+     * @return A {@code LocalDateTime} object indicating reminder deadline
+     * @throws IllegalArgumentException


Missing description for exception

Kobot7 · 2024-10-26T11:19:39Z

src/main/java/fittrack/parser/Parser.java

+            // Try to parse with time (dd/MM/yyyy HH:mm:ss)
+            try {
+                return LocalDateTime.parse(inputDeadline, dateTimeFormatter);
+            } catch (DateTimeParseException e) {


Use more descriptive variable names, it is unclear what "e" refers to

Kobot7 · 2024-10-26T11:20:57Z

src/main/java/fittrack/reminder/Reminder.java

+
+    public void printReminderDescription() {
+        System.out.print(this.reminderDescription + " | " +
+                this.reminderDeadline.format(DateTimeFormatter.ofPattern("dd/MM/yyyy HH:mm")) + System.lineSeparator());


Line length should be no longer than 120 chars

Kobot7 · 2024-10-26T11:31:04Z

src/main/java/fittrack/fitnessgoal/AddFitnessGoal.java

+
+    public void addGoal(User user) {
+        user.addGoal(goal); // Add the goal object to the user's goal list
+        // Use the correct method to get the description of the goal


Comments should explain the WHAT and WHY aspects of the code, rather than the HOW aspect. In this case, a comment may not be necessary

Kobot7 · 2024-10-26T11:33:09Z

src/main/java/fittrack/fitnessgoal/Goal.java

+    private final String description;
+    private final LocalDateTime deadline;
+
+    // Constructor


Would be good to follow Javadoc format to document methods instead

Kobot7 · 2024-10-26T11:34:17Z

src/main/java/fittrack/fitnessgoal/Goal.java

+        return deadline;
+    }
+
+    // Optionally, you might want to override the toString() method for easy printing


Was this comment intended?

Kobot7 · 2024-10-26T11:43:20Z

src/main/java/fittrack/parser/Parser.java

+        case "add-goal":  // use "add-goal" consistently in input and command handling
+            if (!description.isEmpty()) {
+                String[] goalParts = description.split(" ", 2);
+                String goalDescription = goalParts[0];
+                LocalDateTime goalDeadline = null;
+
+                if (goalParts.length > 1) {
+                    String goalDeadlineInput = goalParts[1];
+                    try {
+                        goalDeadline = parseGoalDeadline(goalDeadlineInput);
+                    } catch (IllegalArgumentException e) {
+                        System.out.println("Invalid date format: " + e.getMessage());
+                        return;
+                    }
+                }
+                Goal newGoal = new Goal(goalDescription, goalDeadline);
+                goalList.add(newGoal);
+                printAddedGoal(goalList);
+            } else {
+                System.out.println("Please specify a goal to add.");
+            }
+            break;


Avoid deep nesting

Kobot7 · 2024-10-26T11:45:08Z

src/main/java/fittrack/parser/Parser.java

+            String inputDeadline = sentence[1];
+            description = sentence[0];
+
+            assert !description.isEmpty() : "Reminder description must not be empty";


Is this intended to be an assertion or exception?

shyaamald · 2024-10-30T04:16:37Z

docs/DeveloperGuide.md

@@ -6,8 +6,77 @@

 ## Design & implementation

+# High Level Functionalities
+![HighLevel.png](HighLevel.png)


Are the arrows standard?

shyaamald · 2024-10-30T04:19:36Z

docs/DeveloperGuide.md

@@ -6,8 +6,77 @@

 ## Design & implementation

+# High Level Functionalities
+![HighLevel.png](HighLevel.png)


Could the roles be closer to the arrow?

shyaamald · 2024-10-30T04:21:28Z

docs/DeveloperGuide.md

+
+The following sequence diagram illustrates the function calls involved in this process:
+
+![editExerciseSequenceDiagram.png](editExerciseSequenceDiagram.png)


Stickman is not standard here

shyaamald · 2024-10-30T04:24:54Z

docs/DeveloperGuide.md

+
+The following sequence diagram illustrates the function calls involved in this process:
+
+![editExerciseSequenceDiagram.png](editExerciseSequenceDiagram.png)


Could activation bars be added?

shyaamald · 2024-10-30T04:37:45Z

docs/DeveloperGuide.md

+
+3. **Calculator Logic**: The calculator class uses a lookup table, which maps the user's performance 
+   to points based on their age and gender. The points are returned to the exercise station, where they are stored.
+

 ## Product scope


Could add own user stories

shyaamald · 2024-10-30T04:47:55Z

docs/DeveloperGuide.md

+Additionally, the state diagram below shows the end state of the `editExercise` function after execution of the command,
+`editExercise(Exercise.PULL_UP, 1)`:
+
+![TrainingSessionEditState.png](TrainingSessionEditState.png)


This is not a state diagram

Progresst-8

DG looks mostly okay, but some amendments are required.
Some parts of the DG are still left unchanged from the template. Those should be updated to reflect your project.

Progresst-8 · 2024-10-30T04:20:07Z

docs/TrainingSessionEditState.png

What is the relation between ExerciseStation class and the 6 station classes below? Is there some kind of inheritance?

The class diagram has non-standard notation such as:
visibility
class label
arrowhead

Progresst-8 · 2024-10-30T04:24:42Z

docs/DeveloperGuide.md

+
+![editExerciseSequenceDiagram.png](editExerciseSequenceDiagram.png)
+
+Additionally, the state diagram below shows the end state of the `editExercise` function after execution of the command,


The state diagram is a specific kind of UML behavioral diagram.

Additionally, the state diagram below ...

I don't think that's what you're referring to here, as this seems like structural?
Additionally, is this a class diagram or an object diagram? It contains the non-underlined name (like a class diagram) and values of variables (like an object diagram)

Progresst-8 · 2024-10-30T04:32:11Z

docs/editExerciseSequenceDiagram.png

Why is the Parser class represented by a stickfigure? Doesn't the stickfigure represent a user, not a class?

The instance name is missing the colon before it, as per Sequence diagram conventions.

Why are the activation bars missing?

Does Parser have a custom-defined print method, since print() is pointing to Parser? If so, why is a Parser printing (writing to output), when it should be parsing (reading from input)?

Progresst-8 · 2024-10-30T04:38:29Z

docs/DeveloperGuide.md

+
+3. **Calculator Logic**: The calculator class uses a lookup table, which maps the user's performance 
+   to points based on their age and gender. The points are returned to the exercise station, where they are stored.
+


Are the user stories below still unchanged from the template?
Where are the user stories for your project?

Progresst-8 · 2024-10-30T04:46:33Z

docs/HighLevel.png

Is this supposed to be a high-level overview of your entire program? Inclusion of low-level implementation details seems counter to what an overview is supposed to do.
If so, isn't a class diagram not appropriate for this purpose?
Perhaps this should be an architecture diagram instead of a class diagram?

Additionally, for a class diagram, labels require the arrowhead, which is not present here.

rharwo · 2024-10-30T06:21:55Z

docs/DeveloperGuide.md

+initializes an EnumMap, which populates the various `ExerciseStation` instances with their initial values. 
+Below is a representation of how the `ExerciseStations` are initialized:
+
+![TrainingSessionInitialState.png](TrainingSessionInitialState.png)  


Unclear what the visibility is in this class diagram

rharwo · 2024-10-30T06:26:50Z

docs/DeveloperGuide.md

@@ -6,8 +6,77 @@

 ## Design & implementation

+# High Level Functionalities
+![HighLevel.png](HighLevel.png)


Somewhat complex class diagram. Maybe split into components?

rharwo · 2024-10-30T06:33:44Z

docs/DeveloperGuide.md

+
+The following sequence diagram illustrates the function calls involved in this process:
+
+![editExerciseSequenceDiagram.png](editExerciseSequenceDiagram.png)


I believe doesn't follow correct format for class name. I think it should be ":ClassName"

rharwo · 2024-10-30T06:35:13Z

docs/DeveloperGuide.md

+
+The following sequence diagram illustrates the function calls involved in this process:
+
+![editExerciseSequenceDiagram.png](editExerciseSequenceDiagram.png)


Should Parser be shown as an object? i.e. should it be in a box?

rharwo · 2024-10-30T06:39:36Z

docs/DeveloperGuide.md

+method. The main responsibility of this method is to invoke the `calculatePoints()` function from the 
+respective **calculator** class (e.g., `PullUpCalculator`, `SitUpCalculator`), which holds the points calculation logic.
+
+![getPointsSequenceDiagram.png](getPointsSequenceDiagram.png)


Should sequence diagram return arrows be labeled "return {variable}" or just "variable"?

rharwo · 2024-10-30T06:44:15Z

docs/DeveloperGuide.md

+method. The main responsibility of this method is to invoke the `calculatePoints()` function from the 
+respective **calculator** class (e.g., `PullUpCalculator`, `SitUpCalculator`), which holds the points calculation logic.
+
+![getPointsSequenceDiagram.png](getPointsSequenceDiagram.png)


Could the "PullUpStation" and "PullUpCalculator" be named to be generic names to showcase what is written in the description?

rharwo · 2024-10-30T06:47:08Z

docs/DeveloperGuide.md

+
+The following sequence diagram illustrates the function calls involved in this process:
+
+![editExerciseSequenceDiagram.png](editExerciseSequenceDiagram.png)


Should activation bars be either added here or removed in the next sequence diagram to follow a standard format?

DucPhong135 · 2024-11-02T12:46:50Z

docs/DeveloperGuide.md

This diagram is abit hard to look at

DucPhong135 · 2024-11-02T12:50:02Z

docs/DeveloperGuide.md

The relationship label can be placed uniformly for better layout

DucPhong135 · 2024-11-02T12:54:06Z

docs/DeveloperGuide.md

the use of the uses label on all associations might be redundant, as it doesn’t add much information and could be removed for a cleaner look

DucPhong135 · 2024-11-02T12:56:45Z

docs/DeveloperGuide.md

If Calculator is intended to be a shared utility, can the relationship between Calculator and ExerciseStation changed to a dependency that is accessed via FitTrack or TrainingSession instead?

DucPhong135 · 2024-11-02T12:57:31Z

docs/DeveloperGuide.md

Overall, really well structured DG, diagrams really clarify the functionalities of the app

…into 205-docs-update-dg-for-v20 # Conflicts: # docs/DeveloperGuide.md

# Conflicts: # FitTrackLogger.log

205 docs update dg for v20

Branch: Update DG

…alities

Docs: Update DG for V2.0

…into 205-docs-update-dg-for-high-level-functionalities

…el-functionalities 205 docs update dg for high level functionalities

…aphing-functionalities 233 implement user input for graphing functionalities

…contribution-update

- include functionality of Calculator class - include PUML diagram for graphPerformanceTime

Fix formatting for table.

Updated PPP

Final ppp

Update thedinos ppp.

remove duplicate

shorten description

Update README to reflect UG.

Update ug dg

…into 367-refactor-ppp-name

Refactor AboutUs

Kobot7 reviewed Oct 22, 2024

View reviewed changes

Kobot7 reviewed Oct 26, 2024

View reviewed changes

shyaamald reviewed Oct 30, 2024

View reviewed changes

Progresst-8 reviewed Oct 30, 2024

View reviewed changes

rharwo reviewed Oct 30, 2024

View reviewed changes

DucPhong135 reviewed Nov 2, 2024

View reviewed changes

docs/DeveloperGuide.md

Copy link

DucPhong135 Nov 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This diagram is abit hard to look at

DucPhong135 reviewed Nov 2, 2024

View reviewed changes

docs/DeveloperGuide.md

Copy link

DucPhong135 Nov 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The relationship label can be placed uniformly for better layout

DucPhong135 reviewed Nov 2, 2024

View reviewed changes

docs/DeveloperGuide.md

Copy link

DucPhong135 Nov 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, really well structured DG, diagrams really clarify the functionalities of the app

Zackermax and others added 20 commits November 7, 2024 14:18

Merge branch 'master' of https://github.com/AY2425S1-CS2113-W13-2/tp …

8f035e7

…into 205-docs-update-dg-for-v20 # Conflicts: # docs/DeveloperGuide.md

Merge branch 'master' of https://github.com/Yvorm/tp

de93e86

# Conflicts: # FitTrackLogger.log

Merge pull request #228 from Zackermax/205-docs-update-dg-for-v20

b786d9a

205 docs update dg for v20

Merge branch 'master' of https://github.com/Yvorm/tp

c362a33

fix: correct return arrows in addTrainingSession puml diagram

e1591c7

feat: add GraphPerformanceTime class section in developer guide

75d8979

Docs: Update DG for V2.0

b028922

Merge pull request #230 from CheeKiangg/Branch-UpdateDG

a5c7bc6

Branch: Update DG

Update DG for graph features.

93aeb62

Merge branch 'master' into 205-docs-update-dg-for-high-level-function…

29ca26a

…alities

Merge pull request #231 from Zackermax/205-docs-update-dg-for-v20-2

b4d6db1

Docs: Update DG for V2.0

Merge branch 'master' of https://github.com/AY2425S1-CS2113-W13-2/tp …

b746292

…into 205-docs-update-dg-for-high-level-functionalities

Merge pull request #232 from TheDinos/205-docs-update-dg-for-high-lev…

3f2cedc

…el-functionalities 205 docs update dg for high level functionalities

Update minor error in DG.

bb19f78

Implement graphing functionality for user input.

e1f2ce6

Fix checkstyle.

3baea89

Update checkstyle.

f6c3de1

Merge pull request #234 from TheDinos/233-implement-user-input-for-gr…

11f8d5a

…aphing-functionalities 233 implement user input for graphing functionalities

Merge remote-tracking branch 'origin/update-UserGuide-V2' into dg-ug-…

da7d9a1

…contribution-update

feat: update DG

ea1cbfd

- include functionality of Calculator class - include PUML diagram for graphPerformanceTime

TheDinos and others added 30 commits November 12, 2024 11:34

Merge pull request #360 from TheDinos/358-final-update-to-ppp

07b9755

Fix formatting for table.

Updated PPP

c6b71c5

Merge branch 'PPP-finalisedversion' into FinalPPP

12aa540

remove duplicate

5b2f65a

Update thedinos ppp.

97682a8

Merge pull request #362 from Yvorm/update-PPP-AvjayBhar

bcc6982

Updated PPP

Merge pull request #361 from CheeKiangg/FinalPPP

5e2efc9

Final ppp

Merge pull request #363 from TheDinos/358-final-update-to-ppp2

3679bc7

Update thedinos ppp.

Merge branch 'master' into FinalPPPv2.1

d5370c7

Merge pull request #364 from CheeKiangg/FinalPPPv2.1

e9394fc

remove duplicate

Update UG

4717a5b

Merge branch 'master' into update-UG

2769193

shorten description

c3ee374

Merge pull request #365 from CheeKiangg/PPP_v

61d432e

shorten description

Add PPP

3b8d23b

Update README to reflect UG.

38e3631

Merge pull request #366 from TheDinos/358-final-update-to-readme

24d05a7

Update README to reflect UG.

Add files via upload

43c9494

Add DG diagrams / UML

15c0e04

Update Reminder-related DG entries

7746629

Update Storage Class diagram

77c7e1a

Add misc Updates to DG

3b34ba1

Update Documentation

639c903

Refactor PPP

bfe6bf4

Refactor PPP

78479f9

Merge pull request #368 from Yvorm/update-UG-DG

06fe873

Update ug dg

Merge branch 'master' of https://github.com/AY2425S1-CS2113-W13-2/tp …

8da8723

…into 367-refactor-ppp-name

Merge pull request #369 from Zackermax/367-refactor-ppp-name

e2aee92

Refactor AboutUs

97cd54f

Merge pull request #371 from Zackermax/370-refactor-aboutus

5a63a3f

Refactor AboutUs

		private static final Map<LookUpKey, TreeMap<Integer, Integer>> pullUpTable = new HashMap<>();
		private static final boolean reverseOrder = true;

		public static final String SAVE_FILE = "data/saveFile.txt"; // Path to the save file
		public static final File SAVEFILE = new File(SAVE_FILE); // File object for the save file


		The following sequence diagram illustrates the function calls involved in this process:

		![editExerciseSequenceDiagram.png](editExerciseSequenceDiagram.png)


		![editExerciseSequenceDiagram.png](editExerciseSequenceDiagram.png)

		Additionally, the state diagram below shows the end state of the `editExercise` function after execution of the command,


		3. Calculator Logic: The calculator class uses a lookup table, which maps the user's performance
		to points based on their age and gender. The points are returned to the exercise station, where they are stored.

[CS2113-W13-2] FitTrack #22

Are you sure you want to change the base?

[CS2113-W13-2] FitTrack #22

Conversation

TheDinos commented Sep 25, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Progresst-8 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment