Views
No views yet
pip install -U sentence-transformers1from sentence_transformers import CrossEncoder
2
3# Download from the 🤗 Hub
4model = CrossEncoder("maennyn/pv211_beir_cqadupstack_crossencoder2")
5# Get scores for pairs of texts
6pairs = [
7 ['Increase the X length of a tikzpicture', "In recent years I've developed a habit of formatting SQL `SELECT` queries like so: SELECT fieldNames FROM sources JOIN tableSource ON col1 = col2 JOIN ( SELECT fieldNames FROM otherSources ) AS subQuery ON subQuery.foo = col2 WHERE someField = somePredicate So you see my pattern: each keyword is on its own line and that keyword's fields are indented by 1 tab-stop and the pattern is used recursively for sub- queries. This works well for all of my `SELECT` queries, as it maximizes readability though at the cost of vertical space; but it doesn't work for things like `INSERT` and `UPDATE` which have radically different syntax. INSERT INTO tableName ( col1, col2, col3, col4, col5, col6, col7, col8 ) VALUES ( 'col1', 'col2', 'col3', 'col4', 'col5', 'col6', 'col7', 'col8' ), VALUES ( 'col1', 'col2', 'col3', 'col4', 'col5', 'col6', 'col7', 'col8' ) UPDATE tableName SET col1 = 'col1', col2 = 'col2', col3 = 'col3', // etc WHERE someField = somePredicate As you can see, they aren't as pretty, and when you're dealing with tables with a lot of columns they quickly become unweildly. Is there a better way to format `INSERT` and `UPDATE`? And what about `CREATE` statements and other operations?"],
8 ['Fillable form: checkbox linked to hide/unhide sections; pushbutton to add/delete rows', "I'd like to create a LaTeX document that when rendered into PDF, has forms that can be filled out using Adobe Reader or other such programs. Then I'd like to be able to extract the data. I deliberately would like to avoid using Acrobat for all the usual reasons (non-free, need different versions for different platforms etc). Can this be done ?"],
9 ['Is there any way to get something like pmatrix with customizable grid lines between cells?', "> **Possible Duplicate:** > Highlight elements in the matrix i have a matrix: \\begin{equation} \\begin{bmatrix} 1 & 5 & 4 & 2 & 1 \\\\ 1 & 5 & 4 & 2 & 1 \\\\ 1 & 5 & 4 & 2 & 1 \\\\ \\end{bmatrix} \\label{e:crop1} \\end{equation} and i would like to draw a box around a few of the values to highlight a selection & label it, how would i go about this? I've looked at nodes but havent got a clue. thanks"],
10 ["Difference between 'all' and 'all the'", 'I am not confident about my judgement as to whether or not "the" is required if a relative clause is used in a sentence. For example, > The data can be collected on all the computers on which the software is > installed. I think it must be "all the computers " and not be "all computers" because "computers" is specified by "on which the software is installed". Please help me confirm that I am right.'],
11 ['Understanding the exclamation mark (!) in bash', "I'm following through a tutorial and it mentions to run this command: sudo chmod 700 !$ I'm not familiar with `!$`. What does it mean?"],
12]
13scores = model.predict(pairs)
14print(scores.shape)
15# (5,)
16
17# Or rank different texts based on similarity to a single text
18ranks = model.rank(
19 'Increase the X length of a tikzpicture',
20 [
21 "In recent years I've developed a habit of formatting SQL `SELECT` queries like so: SELECT fieldNames FROM sources JOIN tableSource ON col1 = col2 JOIN ( SELECT fieldNames FROM otherSources ) AS subQuery ON subQuery.foo = col2 WHERE someField = somePredicate So you see my pattern: each keyword is on its own line and that keyword's fields are indented by 1 tab-stop and the pattern is used recursively for sub- queries. This works well for all of my `SELECT` queries, as it maximizes readability though at the cost of vertical space; but it doesn't work for things like `INSERT` and `UPDATE` which have radically different syntax. INSERT INTO tableName ( col1, col2, col3, col4, col5, col6, col7, col8 ) VALUES ( 'col1', 'col2', 'col3', 'col4', 'col5', 'col6', 'col7', 'col8' ), VALUES ( 'col1', 'col2', 'col3', 'col4', 'col5', 'col6', 'col7', 'col8' ) UPDATE tableName SET col1 = 'col1', col2 = 'col2', col3 = 'col3', // etc WHERE someField = somePredicate As you can see, they aren't as pretty, and when you're dealing with tables with a lot of columns they quickly become unweildly. Is there a better way to format `INSERT` and `UPDATE`? And what about `CREATE` statements and other operations?",
22 "I'd like to create a LaTeX document that when rendered into PDF, has forms that can be filled out using Adobe Reader or other such programs. Then I'd like to be able to extract the data. I deliberately would like to avoid using Acrobat for all the usual reasons (non-free, need different versions for different platforms etc). Can this be done ?",
23 "> **Possible Duplicate:** > Highlight elements in the matrix i have a matrix: \\begin{equation} \\begin{bmatrix} 1 & 5 & 4 & 2 & 1 \\\\ 1 & 5 & 4 & 2 & 1 \\\\ 1 & 5 & 4 & 2 & 1 \\\\ \\end{bmatrix} \\label{e:crop1} \\end{equation} and i would like to draw a box around a few of the values to highlight a selection & label it, how would i go about this? I've looked at nodes but havent got a clue. thanks",
24 'I am not confident about my judgement as to whether or not "the" is required if a relative clause is used in a sentence. For example, > The data can be collected on all the computers on which the software is > installed. I think it must be "all the computers " and not be "all computers" because "computers" is specified by "on which the software is installed". Please help me confirm that I am right.',
25 "I'm following through a tutorial and it mentions to run this command: sudo chmod 700 !$ I'm not familiar with `!$`. What does it mean?",
26 ]
27)
28# [{'corpus_id': ..., 'score': ...}, {'corpus_id': ..., 'score': ...}, ...]sts_devCrossEncoderCorrelationEvaluator| Metric | Value |
|---|---|
| pearson | 0.8858 |
| spearman | 0.8182 |
NanoMSMARCO_R100, NanoNFCorpus_R100 and NanoNQ_R100CrossEncoderRerankingEvaluator with these parameters:
1{
2 "at_k": 10,
3 "always_rerank_positives": true
4}| Metric | NanoMSMARCO_R100 | NanoNFCorpus_R100 | NanoNQ_R100 |
|---|---|---|---|
| map | 0.6048 (+0.1152) | 0.3633 (+0.1023) | 0.6871 (+0.2674) |
| mrr@10 | 0.5974 (+0.1199) | 0.5961 (+0.0962) | 0.7117 (+0.2850) |
| ndcg@10 | 0.6644 (+0.1240) | 0.4082 (+0.0832) | 0.7413 (+0.2407) |
NanoBEIR_R100_meanCrossEncoderNanoBEIREvaluator with these parameters:
1{
2 "dataset_names": [
3 "msmarco",
4 "nfcorpus",
5 "nq"
6 ],
7 "rerank_k": 100,
8 "at_k": 10,
9 "always_rerank_positives": true
10}| Metric | Value |
|---|---|
| map | 0.5517 (+0.1616) |
| mrr@10 | 0.6350 (+0.1670) |
| ndcg@10 | 0.6046 (+0.1493) |
query, document, and label| query | document | label | |
|---|---|---|---|
| type | string | string | int |
| details |
|
|
|
| query | document | label |
|---|---|---|
Increase the X length of a tikzpicture | In recent years I've developed a habit of formatting SQL [object Object] queries like so: SELECT fieldNames FROM sources JOIN tableSource ON col1 = col2 JOIN ( SELECT fieldNames FROM otherSources ) AS subQuery ON subQuery.foo = col2 WHERE someField = somePredicate So you see my pattern: each keyword is on its own line and that keyword's fields are indented by 1 tab-stop and the pattern is used recursively for sub- queries. This works well for all of my [object Object] queries, as it maximizes readability though at the cost of vertical space; but it doesn't work for things like [object Object] and [object Object] which have radically different syntax. INSERT INTO tableName ( col1, col2, col3, col4, col5, col6, col7, col8 ) VALUES ( 'col1', 'col2', 'col3', 'col4', 'col5', 'col6', 'col7', 'col8' ), VALUES ( 'col1', 'col2', 'col3', 'col4',... | 0 |
Fillable form: checkbox linked to hide/unhide sections; pushbutton to add/delete rows | I'd like to create a LaTeX document that when rendered into PDF, has forms that can be filled out using Adobe Reader or other such programs. Then I'd like to be able to extract the data. I deliberately would like to avoid using Acrobat for all the usual reasons (non-free, need different versions for different platforms etc). Can this be done ? | 1 |
Is there any way to get something like pmatrix with customizable grid lines between cells? | > [object Object] > Highlight elements in the matrix i have a matrix: \begin{equation} \begin{bmatrix} 1 & 5 & 4 & 2 & 1 \ 1 & 5 & 4 & 2 & 1 \ 1 & 5 & 4 & 2 & 1 \ \end{bmatrix} \label{e:crop1} \end{equation} and i would like to draw a box around a few of the values to highlight a selection & label it, how would i go about this? I've looked at nodes but havent got a clue. thanks | 1 |
BinaryCrossEntropyLoss with these parameters:
1{
2 "activation_fn": "torch.nn.modules.linear.Identity",
3 "pos_weight": null
4}eval_strategy: epochper_device_train_batch_size: 16per_device_eval_batch_size: 16learning_rate: 2e-05warmup_ratio: 0.1save_only_model: Truefp16: Trueload_best_model_at_end: Trueoverwrite_output_dir: Falsedo_predict: Falseeval_strategy: epochprediction_loss_only: Trueper_device_train_batch_size: 16per_device_eval_batch_size: 16per_gpu_train_batch_size: Noneper_gpu_eval_batch_size: Nonegradient_accumulation_steps: 1eval_accumulation_steps: Nonetorch_empty_cache_steps: Nonelearning_rate: 2e-05weight_decay: 0.0adam_beta1: 0.9adam_beta2: 0.999adam_epsilon: 1e-08max_grad_norm: 1.0num_train_epochs: 3max_steps: -1lr_scheduler_type: linearlr_scheduler_kwargs: {}warmup_ratio: 0.1warmup_steps: 0log_level: passivelog_level_replica: warninglog_on_each_node: Truelogging_nan_inf_filter: Truesave_safetensors: Truesave_on_each_node: Falsesave_only_model: Truerestore_callback_states_from_checkpoint: Falseno_cuda: Falseuse_cpu: Falseuse_mps_device: Falseseed: 42data_seed: Nonejit_mode_eval: Falseuse_ipex: Falsebf16: Falsefp16: Truefp16_opt_level: O1half_precision_backend: autobf16_full_eval: Falsefp16_full_eval: Falsetf32: Nonelocal_rank: 0ddp_backend: Nonetpu_num_cores: Nonetpu_metrics_debug: Falsedebug: []dataloader_drop_last: Falsedataloader_num_workers: 0dataloader_prefetch_factor: Nonepast_index: -1disable_tqdm: Falseremove_unused_columns: Truelabel_names: Noneload_best_model_at_end: Trueignore_data_skip: Falsefsdp: []fsdp_min_num_params: 0fsdp_config: {'min_num_params': 0, 'xla': False, 'xla_fsdp_v2': False, 'xla_fsdp_grad_ckpt': False}tp_size: 0fsdp_transformer_layer_cls_to_wrap: Noneaccelerator_config: {'split_batches': False, 'dispatch_batches': None, 'even_batches': True, 'use_seedable_sampler': True, 'non_blocking': False, 'gradient_accumulation_kwargs': None}deepspeed: Nonelabel_smoothing_factor: 0.0optim: adamw_torchoptim_args: Noneadafactor: Falsegroup_by_length: Falselength_column_name: lengthddp_find_unused_parameters: Noneddp_bucket_cap_mb: Noneddp_broadcast_buffers: Falsedataloader_pin_memory: Truedataloader_persistent_workers: Falseskip_memory_metrics: Trueuse_legacy_prediction_loop: Falsepush_to_hub: Falseresume_from_checkpoint: Nonehub_model_id: Nonehub_strategy: every_savehub_private_repo: Nonehub_always_push: Falsegradient_checkpointing: Falsegradient_checkpointing_kwargs: Noneinclude_inputs_for_metrics: Falseinclude_for_metrics: []eval_do_concat_batches: Truefp16_backend: autopush_to_hub_model_id: Nonepush_to_hub_organization: Nonemp_parameters:auto_find_batch_size: Falsefull_determinism: Falsetorchdynamo: Noneray_scope: lastddp_timeout: 1800torch_compile: Falsetorch_compile_backend: Nonetorch_compile_mode: Noneinclude_tokens_per_second: Falseinclude_num_input_tokens_seen: Falseneftune_noise_alpha: Noneoptim_target_modules: Nonebatch_eval_metrics: Falseeval_on_start: Falseuse_liger_kernel: Falseeval_use_gather_object: Falseaverage_tokens_across_devices: Falseprompts: Nonebatch_sampler: batch_samplermulti_dataset_batch_sampler: proportional| Epoch | Step | Training Loss | sts_dev_spearman | NanoMSMARCO_R100_ndcg@10 | NanoNFCorpus_R100_ndcg@10 | NanoNQ_R100_ndcg@10 | NanoBEIR_R100_mean_ndcg@10 |
|---|---|---|---|---|---|---|---|
| -1 | -1 | - | 0.7222 | 0.6686 (+0.1282) | 0.3930 (+0.0680) | 0.7599 (+0.2592) | 0.6072 (+0.1518) |
| 0.4355 | 1000 | 0.4163 | - | - | - | - | - |
| 0.8711 | 2000 | 0.1632 | - | - | - | - | - |
| 1.0 | 2296 | - | 0.8182 | 0.6644 (+0.1240) | 0.4082 (+0.0832) | 0.7413 (+0.2407) | 0.6046 (+0.1493) |
| 1.3066 | 3000 | 0.1227 | - | - | - | - | - |
| 1.7422 | 4000 | 0.1157 | - | - | - | - | - |
| 2.0 | 4592 | - | 0.8201 | 0.6266 (+0.0862) | 0.4096 (+0.0846) | 0.7032 (+0.2026) | 0.5798 (+0.1244) |
| 2.1777 | 5000 | 0.0964 | - | - | - | - | - |
| 2.6132 | 6000 | 0.081 | - | - | - | - | - |
| 3.0 | 6888 | - | 0.8203 | 0.6241 (+0.0837) | 0.4068 (+0.0817) | 0.6931 (+0.1924) | 0.5747 (+0.1193) |
| -1 | -1 | - | 0.8182 | 0.6644 (+0.1240) | 0.4082 (+0.0832) | 0.7413 (+0.2407) | 0.6046 (+0.1493) |
1@inproceedings{reimers-2019-sentence-bert,
2 title = "Sentence-BERT: Sentence Embeddings using Siamese BERT-Networks",
3 author = "Reimers, Nils and Gurevych, Iryna",
4 booktitle = "Proceedings of the 2019 Conference on Empirical Methods in Natural Language Processing",
5 month = "11",
6 year = "2019",
7 publisher = "Association for Computational Linguistics",
8 url = "https://arxiv.org/abs/1908.10084",
9}