You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So Basileal and I worked together and finished some part of the project, and now Basileal is working on the Javascript randomization and I am (still) troubleshooting the score method and display of the tables.
After some search, it seems my issue is due to the discrepancies of forms, parameters, and table entries, and so I am thinking of applying the following 'fixes'. If there is any issue that may arise from these changes, please inform me!
If the use of versa valve is a characteristic of the robot than a run, then I will be removing versa_valve form from run page and table entry.
There seems to be two form elements that keep track of the number of rooms (one for level 1 and certain divisions, and one for level 2 and room factor application). Their name is rooms_searched and num_rooms_searched, so I am considering to change the names to make their differences more explicit. I will make it so that they go under the same table entry.
There is currently only a boolean value that keeps track of run disqualification. Should we add a table entry to keep track of the reasons of disqualification? If so, should it be string entry, radio buttons, etc?
Thanks again for your help!
The text was updated successfully, but these errors were encountered:
Hi!
So Basileal and I worked together and finished some part of the project, and now Basileal is working on the Javascript randomization and I am (still) troubleshooting the score method and display of the tables.
After some search, it seems my issue is due to the discrepancies of forms, parameters, and table entries, and so I am thinking of applying the following 'fixes'. If there is any issue that may arise from these changes, please inform me!
Thanks again for your help!
The text was updated successfully, but these errors were encountered: