compare_maps
Compares text-only and citation-weighted maps using hidden citation links, coherence, stability, and coverage to recommend a map for S3 community analysis.
Instructions
Before the full analysis: which map should S3 use for this corpus? Compares the text map (the published method) with text plus bibliographic coupling, co-citation or direct citation at 5%, 10%, ... 40% weight; citations count only for pairs already close in content (the text floor). extended=True adds the same grid without the floor. 20% of the in-corpus citation links are hidden while the maps are built; each map is scored on the hidden links inside its communities (gain over random communities of the same sizes), on text coherence (TCI gain over random), stability (ARI across seeds and 90% samples) and coverage. A rule fixed in advance recommends a map. Show the user the table and the recommendation, then pass the chosen map to run_s3_analysis as map_relations. Takes a few minutes; embeddings are cached for the run. With run_id instead of csv_path, compares on that run's papers and citation links: use this after enrich_citations, so the comparison uses the exact Scopus reference lists.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "compare_maps"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| seed | No | ||
| run_id | No | ||
| csv_path | No | ||
| end_year | No | ||
| extended | No | ||
| start_year | No | ||
| embedding_model | No | mpnet | |
| strict_citations | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |