BM25 Baselines for MS MARCO Passage Ranking in Anserini + MS MARCO Evaluation, TREC Evaluation #2663
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Operating System: Ubuntu 20.04.6 LTS Kernel Version: 5.15.0-122-generic Python Version:** 3.8.10 Maven Version: Apache Maven 3.8.1 Memory: 125 GiB Processor: AMD Ryzen 9 5900X 12-Core Processor (12 cores, 24 threads, Base 3.7 GHz, Boost 4.3 GHz) Outcome: All steps completed successfully
Operating System: Windows 10 Home Chinese Version Version: 22H2 Installation Date: January 19, 2022 Build Version: 19045.5247 Processor: AMD Ryzen 7 4800H with Radeon Graphics (Base 2.90 GHz) Memory: 16 GB (15.4 GB usable) System Type: 64-bit Operating System, x64-based Processor Outcome: All steps completed successfully Issues Encountered: Windows Virtual Memory Allocation Issue: High memory usage during inverted index construction caused system memory exhaustion. Solution: Manually increased Windows virtual memory allocation to approximately 200 GB to ensure the indexing process completed smoothly. TREC Tool Incompatibility on Windows: The default trec_eval tool does not support native Windows execution. Solution: Recompiled trec_eval using MSYS2 to successfully execute the tool
Operating System: Windows 10 Home Chinese Version Version: 22H2 Installation Date: January 19, 2022 Build Version: 19045.5247 Processor: AMD Ryzen 7 4800H with Radeon Graphics (Base 2.90 GHz) Memory: 16 GB (15.4 GB usable) System Type: 64-bit Operating System, x64-based Processor Outcome: All steps completed successfully Issues Encountered: Windows Virtual Memory Allocation Issue: High memory usage during inverted index construction caused system memory exhaustion. Solution: Manually increased Windows virtual memory allocation to approximately 200 GB to ensure the indexing process completed smoothly. TREC Tool Incompatibility on Windows: The default trec_eval tool does not support native Windows execution. Solution: Recompiled trec_eval using MSYS2 to successfully execute the tool
Operating System: Windows 10 Home Chinese Version Version: 22H2 Installation Date: January 19, 2022 Build Version: 19045.5247 Processor: AMD Ryzen 7 4800H with Radeon Graphics (Base 2.90 GHz) Memory: 16 GB (15.4 GB usable) System Type: 64-bit Operating System, x64-based Processor Outcome: All steps completed successfully Issues Encountered: Windows Virtual Memory Allocation Issue: High memory usage during inverted index construction caused system memory exhaustion. Solution: Manually increased Windows virtual memory allocation to approximately 200 GB to ensure the indexing process completed smoothly. TREC Tool Incompatibility on Windows: The default trec_eval tool does not support native Windows execution. Solution: Recompiled trec_eval using MSYS2 to successfully execute the tool
Operating System: Windows 10 Home Chinese Version Version: 22H2 Installation Date: January 19, 2022 Build Version: 19045.5247 Processor: AMD Ryzen 7 4800H with Radeon Graphics (Base 2.90 GHz) Memory: 16 GB (15.4 GB usable) System Type: 64-bit Operating System, x64-based Processor Outcome: All steps completed successfully Issues Encountered: Windows Virtual Memory Allocation Issue: High memory usage during inverted index construction caused system memory exhaustion. Solution: Manually increased Windows virtual memory allocation to approximately 200 GB to ensure the indexing process completed smoothly. TREC Tool Incompatibility on Windows: The default trec_eval tool does not support native Windows execution. Solution: Recompiled trec_eval using MSYS2 to successfully execute the tool
|
Please revert changes to all files except for the onboarding docs. |
|
@Linsen-gao-457 please fix conflicts? |
Finish! If there is any problem, plz let me know |
|
This should not be the case: The only files that should have changed are the two |
Oh, sorry! I have already merge the new branch. So should i cancel this pull request now? But i find there are some mistaken format in the md file. like Results reproduced by @Linsen-gao-457 on 2024-12-16 (commit ['a86484a'] instead of Results reproduced by @Linsen-gao-457 on 2024-12-16 (commit a86484a6) This branch has already merged. should i raise another pull request? |
|
My mistake, this PR is defunct; #2664 has already been merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Begin your journey（Forrest）and Anserini: BM25 Baselines for MS MARCO Passage Ranking（Forrest）
First project:
ECEUbnuntu (limitted storage)
Operating System: Ubuntu 20.04.6 LTS
Kernel Version: 5.15.0-122-generic
Python Version:** 3.8.10
Maven Version: Apache Maven 3.8.1
Memory: 125 GiB
Processor: AMD Ryzen 9 5900X 12-Core Processor (12 cores, 24 threads, Base 3.7 GHz, Boost 4.3 GHz)
Outcome: All steps completed successfully
Second project:
My computer
Operating System: Windows 10 Home Chinese Version
Version: 22H2
Installation Date: January 19, 2022
Build Version: 19045.5247
Processor: AMD Ryzen 7 4800H with Radeon Graphics (Base 2.90 GHz)
Memory: 16 GB (15.4 GB usable)
System Type: 64-bit Operating System, x64-based Processor
Outcome: All steps completed successfully
Issues Encountered:
Windows Virtual Memory Allocation Issue:
High memory usage during inverted index construction caused system memory exhaustion.
Solution: Manually increased Windows virtual memory allocation to approximately 200 GB to ensure the indexing process completed smoothly.
TREC Tool Incompatibility on Windows: The default trec_eval tool does not support native Windows execution.
Solution: Recompiled trec_eval using MSYS2 to successfully execute the tool
High memory usage during inverted index construction caused system memory exhaustion.
Solution: Manually increased Windows virtual memory allocation to approximately 200 GB to ensure the indexing process completed smoothly.
TREC Tool Incompatibility on Windows: The default trec_eval tool does not support native Windows execution.
Solution: Recompiled trec_eval using MSYS2 to successfully execute the tool