Skip to content

Conversation

@rahul810050
Copy link
Contributor

@rahul810050
Copy link
Contributor Author

@marcgc21 @KarinePistili @sahitya-chandra could you please review it ??

@marcgc21
Copy link
Member

Instead of using the full string, use just SART:

Screenshot 2025-12-31 at 11 11 52

@marcgc21
Copy link
Member

Delete SART summary, the user doesn't need to know what are the value because he/she is just answering:
Screenshot 2025-12-31 at 11 15 22

@marcgc21
Copy link
Member

On SART analytics view it should be done some modifications to match the technique:

On top show:

  • Average SA score
  • Average Demand
  • Average Supply
  • Average Understanding

On SART dimension breakdown:

  • Add a colored values for the bars
  • Group bars on the three group dimensions
  • Fit all the dimensions (right now, "Understanding" doesn't suit well).

On Individual SART Scores:

  • Add a column called "Understanding"

On detail view analytics SART Score:

  • Add the "Understanding Score"

@rahul810050
Copy link
Contributor Author

Thanks for the clarification !! i will update the code according to your feedback @marcgc21

@rahul810050
Copy link
Contributor Author

@marcgc21 I have updated the code according to your feedback

After changing this is how things working...vdo Link

@marcgc21
Copy link
Member

marcgc21 commented Jan 1, 2026

I think that there are conflicts on the language files
Screenshot 2026-01-01 at 12 21 52

@rahul810050
Copy link
Contributor Author

@marcgc21 resolved the conflict. now it is fine

@marcgc21
Copy link
Member

marcgc21 commented Jan 2, 2026

Still have problems. Please take your time to review correctly the PR before uploading again 🙏

Screenshot 2026-01-02 at 07 50 46

@rahul810050
Copy link
Contributor Author

rahul810050 commented Jan 2, 2026

@marcgc21 really sorry about that🙏 I will update the pr asap

@rahul810050
Copy link
Contributor Author

@marcgc21 I have fixed the error. now it is working perfectly fine. once again really sorry about that mistake...

@marcgc21
Copy link
Member

marcgc21 commented Jan 2, 2026

@rahul810050 we still have problems about SART methodology.
Idk where are you taken those dimensions, but "Supply" and "Understanding" are wrong:
Screenshot 2026-01-02 at 14 18 11

You can check this paper:
https://www.researchgate.net/figure/Situation-Awareness-Rating-Technique-SART-10D-Scale-30_fig9_365853339

Basically what it says is that Supply has 4 dimensions ant not 7:

  • Arousal
  • Concentration of Attention
  • Division of Attention
  • Spare Mental Capacity

And "Understanding" has:

  • Information Quantity
  • Information Quality
  • Familiarity with Situation

So basically you are grouping Supply and Understanding. Try to fix this problem and I beliave everything will be done!

category: 'supply'
},
{
key: 'understanding',
Copy link
Member

Choose a reason for hiding this comment

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

This should be the category "Understanding (U)"

category: 'supply'
},
{
key: 'informationQuantity',
Copy link
Member

Choose a reason for hiding this comment

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

InformationQuantity, InformationQuality and Familiarity are from "Understanding" category

@github-actions
Copy link

github-actions bot commented Jan 3, 2026

⚠️ PR Description Issues Detected

Please update the PR description to address these issues.

@rahul810050
Copy link
Contributor Author

rahul810050 commented Jan 3, 2026

@marcgc21 i have updated according to your feedback comments research paper. Just so you know i have changed the ui of sartForm a bit like put some colors according to dimensions just to make it a bit cool. if it seems wrong to you then i can make the ui as same as nasatlx form ui. let me know if you want exact that...

@marcgc21
Copy link
Member

marcgc21 commented Jan 3, 2026

Quality Gate Failed Quality Gate failed

Failed conditions 4.1% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

@rahul810050 can you take a look on that? Also we have fixed the lint action and it is reporting that the code is not fulfilling the requeriments.

Can you also take a look on that? Regardind the feature I bet that it is already done, let's finish that and will finally merge it!

@rahul810050
Copy link
Contributor Author

rahul810050 commented Jan 4, 2026

@marcgc21 i could be wrong but i raised this pr before the updated github actions that is why i think it still uses the previous github actions that is why it is failing....

for example for this #1152 i raised a pr #1199 where i used the same logic in useProfile.js(which fails in two actions same as this current pr) like duplicate staff that i also used in this pr #1266 in ProfileView.vue (but this is the latest develop branch code) and guess what it passes all the checks...i think you get the point marc!!!

if you want i can again raise a new pr for this just to pass the github action let me know if you want that !!!

@marcgc21
Copy link
Member

marcgc21 commented Jan 5, 2026

Hi @rahul810050 I reviewed the lint and it looks like only appears the files that you have modified, so I beliave that it is using the new version

@rahul810050
Copy link
Contributor Author

whole files got lint error I fixed all the files !!! @marcgc21 if you dont want that i will revert these changes

@marcgc21
Copy link
Member

marcgc21 commented Jan 8, 2026

@rahul810050 the problem now is that you applied the lint to the whole project... You need to do it just to the files that you have modified. So please revert the commit to the proper point of time and update it.

@rahul810050 rahul810050 force-pushed the feat/implement-sart-instrument branch from 8fd9ed8 to 8a08047 Compare January 8, 2026 15:16
@rahul810050
Copy link
Contributor Author

@marcgc21 i have reverted the changes. please feel free to review it

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jan 8, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants