Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task 9: Write a script to dump Answer table to CSV file for testers #28

Open
Sourbiebie opened this issue Feb 10, 2022 · 0 comments
Open
Assignees

Comments

@Sourbiebie
Copy link
Contributor

Sourbiebie commented Feb 10, 2022

On 2022/2/9 meeting, it is requested to have a script to dump Answer table for each user. For testing purpose.

@Sourbiebie Sourbiebie self-assigned this Feb 10, 2022
Sourbiebie added a commit that referenced this issue Feb 16, 2022
yalgorithm777 pushed a commit that referenced this issue Mar 2, 2022
* Task 1
#9
Task 1: implement the location table (table structure, operation functions, and testing functions) #9

* Adapted to the data model after 1103 discussion
1. Update the location model and its operation for the data model update
2. Add/Update test cases to support the updated data model
   update_location_bbox_by_id
   update_location_basic_by_id
   create_location

* Code Review Update
1. Comply  to the coding standard / numpydoc style guide
2. Set location table/year non-nullable, remove default value, and add type check

* Update location table
Compliant to the data model update on 11/17:
1. Move display information to answers
2. Add  get_locations for API

* Compliant to coding standard
1. Remove spaces around = for default value
2. Don't use "l" as variable name
3. Remove boolean comparison

* Add function for statistic API
implement get_location_is_done_count and its test function

* Fix gold_standard_size 0 bug and add get_location_count
1. Enhance exception string
2. fix the None list bug when gold_standard_size 0
3. Add get_location_count()

* Add test_get_location_count

* Update get_locations() and test function
Exclude user answered locations when picking locations.

* Update user model and answer model
Upload the code for answer and user table when implementing the location table.

* Update for the code review
1. Add check_answer_correctness for Answer API
2. Fix the parameter from client_id to user_id for API
3. Change get_user_done_location_count design according to the answer create process clarified  on 12/1

* Update answer and location_done algorithm
1. Change Answer. is_gold_standard to gold_standard_status
2. Add batch_process_answers and location done_at algorithm, and its test code
3. Modify get_locations to exclude done done locations.

* Enhance function name and add test case
1. Change check_answer_quality to exam_gold_standard
2. Change check_gold_candidate_status to is_answer_reliable
3. Add test case to is_answer_reliable

* Move batch_process_answer to answer_operation
Code clean up and move batch_process_answer and its test function to answer_operation

* Allow bbox*, zoom_level not required
In create_answer, make bounding box and zoom level parameters optional for gold answers.

* Update is_answer_reliable
1. Explain more clearly
2. Remove redundant code to make it simpler

* Make batch_process_answers more readable
Add gold_test_pass_status documents and default value

* Change answer_count to all answers
1. Change this function to get all answers (not excluding gold standards)
2. Add exception handlers for batch_process_answers

* Add sourc_url_root checking
1. Add sourc_url_root checking
2. Add test case for checking it

* Enhance the error messages
When missing parameters, give clear error message.

* Initial for utilities
Add utilities for importing gold standards and location table from CSV.

* Fix CORS and add answer tests

* Create export_answers.py
#28

* Add client_id and factory_id
Dump more "readable" data for testers.

* Add year_old, year_new to access photo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant