finetuned_mbert

SentenceTransformer based on nomic-ai/modernbert-embed-base

This is a sentence-transformers model finetuned from nomic-ai/modernbert-embed-base. It maps sentences & paragraphs to a 768-dimensional dense vector space and can be used for semantic textual similarity, semantic search, paraphrase mining, text classification, clustering, and more.

Model Details

Model Description

• Model Type: Sentence Transformer
• Base model: nomic-ai/modernbert-embed-base <!-- at revision d556a88e332558790b210f7bdbe87da2fa94a8d8 -->
• Maximum Sequence Length: 8192 tokens
• Output Dimensionality: 768 dimensions
• Similarity Function: Cosine Similarity

<!-- - **Training Dataset:** Unknown --> <!-- - **Language:** Unknown --> <!-- - **License:** Unknown -->

Model Sources

• Documentation: Sentence Transformers Documentation
• Repository: Sentence Transformers on GitHub
• Hugging Face: Sentence Transformers on Hugging Face

Full Model Architecture

SentenceTransformer(
  (0): Transformer({'max_seq_length': 8192, 'do_lower_case': False}) with Transformer model: ModernBertModel 
  (1): Pooling({'word_embedding_dimension': 768, 'pooling_mode_cls_token': False, 'pooling_mode_mean_tokens': True, 'pooling_mode_max_tokens': False, 'pooling_mode_mean_sqrt_len_tokens': False, 'pooling_mode_weightedmean_tokens': False, 'pooling_mode_lasttoken': False, 'include_prompt': True})
  (2): Normalize()
)

Usage

Direct Usage (Sentence Transformers)

First install the Sentence Transformers library:

pip install -U sentence-transformers

Then you can load this model and run inference.

from sentence_transformers import SentenceTransformer

# Download from the 🤗 Hub
model = SentenceTransformer("sentence_transformers_model_id")
# Run inference
sentences = [
    'What is the primary purpose of the FITS format?',
    'FITS format\n\nAll of the ODF/SDF component files, with the exception of the summary\nfiles, reconstructed orbit file, and raw attitude file, are FITS files\nand conform to the standard. A description of the FITS format can be\nfound in , which is accessible also at the URL\nThe calibration files and the bulk of the PPS products also conform to\nthe FITS standard. Wherever possible and desirable the calibration files\nand the PPS products follow the conventions of the OGIP\n(http://heasarc.gsfc.nasa.gov/docs/heasarc/ofwg/ofwg_intro.html) (Office\nof Guest Investigator Programs) FITS working group. The HEASARC FITS\nWorking Group activities are described at the following URL:\nFor FITS files where OGIP FITS standards are not applicable or\navailable, new standards closely following the OGIP approach are used.\n\nThe FITS format is primarily designed to store scientific data sets\nconsisting of multidimensional arrays (1-D spectra, 2-D images or 3-D\ndata cubes) and 2-dimensional tables containing rows and columns of\ndata. A FITS data file is composed of a sequence of Header + Data Units\n(HDUs).\n\nThe general structure of a FITS file is as follows:\n\n-   a primary header;\n\n-   a primary data array of zero length;\n\n-   zero or more extensions\n\nEach extension consists of an extension header and a data section.\nExtensions are named and can appear in any order. Only the following\nFITS extensions are used:\n\n-   ASCII table: XTENSION=TABLE\n\n-   binary table: XTENSION=BINTABLE\n\n-   image: XTENSION=IMAGE\n\nThe header consists of keyword=value statements, which describe the\norganisation of the data in the HDU and the format of the contents. It\nmay also provide additional information, for example, about instrument\nstatus or the history of the data. The following block contains the\ndata, which are structured as specified in the header. The data section\nof the HDU may contain a digital image, a table or a multidimensional\nmatrix that is not an image. An HDU need not contain data.\n',
    'ASCII\n\nASCII files are used to present script and some tabular information. In\nparticular, each ODF/SDF contains a single summary file, with a summary\nof the information relating to the observation or slew (see\nSect.\xa0[dfhb:par:odf]).\n',
]
embeddings = model.encode(sentences)
print(embeddings.shape)
# [3, 768]

# Get the similarity scores for the embeddings
similarities = model.similarity(embeddings, embeddings)
print(similarities.shape)
# [3, 3]

<!-- ### Direct Usage (Transformers) <details><summary>Click to see the direct usage in Transformers</summary> </details> --> <!-- ### Downstream Usage (Sentence Transformers) You can finetune this model on your own dataset. <details><summary>Click to expand</summary> </details> --> <!-- ### Out-of-Scope Use *List how the model may foreseeably be misused and address what users ought not to do with the model.* --> <!-- ## Bias, Risks and Limitations *What are the known or foreseeable issues stemming from this model? You could also flag here known failure cases or weaknesses of the model.* --> <!-- ### Recommendations *What are recommendations with respect to the foreseeable issues? For example, filtering explicit content.* -->

Training Details

Training Dataset

Unnamed Dataset

• Size: 3,625 training samples
• Columns: <code>anchor</code> and <code>positive</code>
• Approximate statistics based on the first 1000 samples:

  	anchor	positive
  type	string	string
  details	<ul><li>min: 2 tokens</li><li>mean: 15.71 tokens</li><li>max: 38 tokens</li></ul>	<ul><li>min: 2 tokens</li><li>mean: 412.57 tokens</li><li>max: 3755 tokens</li></ul>

• Samples:

  anchor	positive
  <code>What is the purpose of the document described in the preface?</code>	<code>Preface<br><br>This is the reference document describing the individual XMM-Newton<br>Survey Science Centre (SSC) data product files. It is intended to be of<br>use to software developers, archive administrators and to scientists<br>analysing XMM-Newton data. Please see the SSC data products Interface<br>Control Document (XMM-SOC-ICD-0006-SSC, issue 4.0) for a description of<br>the product group files and other related files that are sent to the<br>SOC.<br><br>This version (4.3) includes changes related to the upgrade to SAS16.0 in<br>the processing pipeline originally developped in 2012 to uniformly<br>process all the XMM data at that time, from which the 3XMM catalogue was<br>derived. Revisions and additions since version 4.2 are identified by<br>change bars at the right of each page.<br><br>This document will continue to evolve through subsequent issues, under<br>indirect control from the SAS and SSC configuration control boards.<br><br>This document is the result of the work of many people. Contributors<br>have included:<br><br>Hermann Brunner, G...</code>
  <code>What version of the document is described in the preface?</code>	<code>Preface<br><br>This is the reference document describing the individual XMM-Newton<br>Survey Science Centre (SSC) data product files. It is intended to be of<br>use to software developers, archive administrators and to scientists<br>analysing XMM-Newton data. Please see the SSC data products Interface<br>Control Document (XMM-SOC-ICD-0006-SSC, issue 4.0) for a description of<br>the product group files and other related files that are sent to the<br>SOC.<br><br>This version (4.3) includes changes related to the upgrade to SAS16.0 in<br>the processing pipeline originally developped in 2012 to uniformly<br>process all the XMM data at that time, from which the 3XMM catalogue was<br>derived. Revisions and additions since version 4.2 are identified by<br>change bars at the right of each page.<br><br>This document will continue to evolve through subsequent issues, under<br>indirect control from the SAS and SSC configuration control boards.<br><br>This document is the result of the work of many people. Contributors<br>have included:<br><br>Hermann Brunner, G...</code>
  <code>What is the main change in version 4.3 of the document?</code>	<code>Preface<br><br>This is the reference document describing the individual XMM-Newton<br>Survey Science Centre (SSC) data product files. It is intended to be of<br>use to software developers, archive administrators and to scientists<br>analysing XMM-Newton data. Please see the SSC data products Interface<br>Control Document (XMM-SOC-ICD-0006-SSC, issue 4.0) for a description of<br>the product group files and other related files that are sent to the<br>SOC.<br><br>This version (4.3) includes changes related to the upgrade to SAS16.0 in<br>the processing pipeline originally developped in 2012 to uniformly<br>process all the XMM data at that time, from which the 3XMM catalogue was<br>derived. Revisions and additions since version 4.2 are identified by<br>change bars at the right of each page.<br><br>This document will continue to evolve through subsequent issues, under<br>indirect control from the SAS and SSC configuration control boards.<br><br>This document is the result of the work of many people. Contributors<br>have included:<br><br>Hermann Brunner, G...</code>

• Loss: <code>CachedMultipleNegativesRankingLoss</code> with these parameters:

  {
      "scale": 1.0,
      "similarity_fct": "get_similarity"
  }
  

Evaluation Dataset

Unnamed Dataset

• Size: 30 evaluation samples
• Columns: <code>anchor</code> and <code>positive</code>
• Approximate statistics based on the first 30 samples:

  	anchor	positive
  type	string	string
  details	<ul><li>min: 10 tokens</li><li>mean: 16.73 tokens</li><li>max: 31 tokens</li></ul>	<ul><li>min: 6 tokens</li><li>mean: 655.37 tokens</li><li>max: 6762 tokens</li></ul>

• Samples:

  anchor	positive
  <code>In pn imaging mode event lists, what is the type of the OFFSETX column?</code>	<code>- In pn event lists this extension contains the CCD columns to which<br> an additional offset is applied to reduce noise (the offset is later<br> subtracted again by the SAS). In the MOS event lists this extension<br> currently defines columns outside the sensitive CCD window, to which<br> formal very high values of the offset are associated. These columns<br> are discarded by the data processing.<br><br>- For MOS imaging mode event lists this extension contains the<br> following columns:<br><br> Name Type Description<br> --------- ---------------- ----------------------------------------------------------<br> RAWX 2-byte INTEGER Row or column of the bad offset<br> OFFSETX 2-byte INTEGER amplitude of additional column offset (0 for row offset)<br> OFFSETY 2-byte INTEGER amplitude of additional row offset (0 for column offset)<br> CCDNR 1-byte CCD where the offset occurs<br><br>- For MOS timing mode event lists this extension contains the...</code>
  <code>What are the three binary table extensions created per source used for?</code>	<code>- This product lists bright sources detected by EPIC which fall in the<br> RGS field of view. It also includes the entries for the proposal<br> position and the on-axis location. EPIC and RGS positions are given,<br> as well as RGS spatial and energy-dispersion angle extraction<br> regions for the sources and a background region.<br><br>- These files are identified using the keyword<br><br> CONTENT = 'RGS SOURCE LIST' / File content<br><br> in the primary header.<br><br>- There are two binary table extensions (SRCLIST and RGSn_BACKGROUND),<br> plus a further three binary table extensions per source<br> (RGSn_SRCm_SPATIAL, RGSn_SRCm_ORDER_1 and RGSn_SRCm_ORDER_2, where n<br> is the number of the RGS (1 or 2) and m is the number of the source.<br><br>- The SRCLIST extension has the following columns:<br><br> Name Type Description<br> -------------- ------------------ ---------------------------------------------------------<br> INDEX 2-byte INTEGER Source inde...</code>
  <code>What is the purpose of the analysis steps outlined in the document?</code>	<code>Structure of the document<br><br>The structure of the present document is as follows:<br><br>- Chapter [sasguide:par:analysis] introduces the investigator to the<br> analysis of XMM-Newton<br> (http://www.cosmos.esa.int/web/xmm-newton/technical-details) data.<br> It provides a brief description of XMM-Newton<br> (http://www.cosmos.esa.int/web/xmm-newton/technical-details)<br> observation and calibration files and outlines the analysis steps<br> required to produce calibrated event files and to extract scientific<br> products.<br><br>- Chapter [sasguide:par:gui] describes the SAS graphical user<br> interface (GUI), a user friendly tool which enables SAS interactive<br> analysis tasks to be run without using the command line.<br><br>- Chapters [sasguide:par:epic], [sasguide:par:rgs] and<br> [sasguide:par:om] describe the SAS analysis steps required to obtain<br> EPIC<br> (http://www.cosmos.esa.int/web/xmm-newton/technical-details-epic),<br> RGS (http://www.cosmos.esa.int/web/xmm-newton/technical-details-r...</code>

• Loss: <code>CachedMultipleNegativesRankingLoss</code> with these parameters:

  {
      "scale": 1.0,
      "similarity_fct": "get_similarity"
  }
  

Training Hyperparameters

Non-Default Hyperparameters

• eval_strategy: steps
• per_device_train_batch_size: 16
• per_device_eval_batch_size: 4
• num_train_epochs: 2
• lr_scheduler_type: constant
• warmup_ratio: 0.1
• bf16: True
• batch_sampler: no_duplicates

All Hyperparameters

<details><summary>Click to expand</summary>

• overwrite_output_dir: False
• do_predict: False
• eval_strategy: steps
• prediction_loss_only: True
• per_device_train_batch_size: 16
• per_device_eval_batch_size: 4
• per_gpu_train_batch_size: None
• per_gpu_eval_batch_size: None
• gradient_accumulation_steps: 1
• eval_accumulation_steps: None
• torch_empty_cache_steps: None
• learning_rate: 5e-05
• weight_decay: 0.0
• adam_beta1: 0.9
• adam_beta2: 0.999
• adam_epsilon: 1e-08
• max_grad_norm: 1.0
• num_train_epochs: 2
• max_steps: -1
• lr_scheduler_type: constant
• lr_scheduler_kwargs: {}
• warmup_ratio: 0.1
• warmup_steps: 0
• log_level: passive
• log_level_replica: warning
• log_on_each_node: True
• logging_nan_inf_filter: True
• save_safetensors: True
• save_on_each_node: False
• save_only_model: False
• restore_callback_states_from_checkpoint: False
• no_cuda: False
• use_cpu: False
• use_mps_device: False
• seed: 42
• data_seed: None
• jit_mode_eval: False
• use_ipex: False
• bf16: True
• fp16: False
• fp16_opt_level: O1
• half_precision_backend: auto
• bf16_full_eval: False
• fp16_full_eval: False
• tf32: None
• local_rank: 0
• ddp_backend: None
• tpu_num_cores: None
• tpu_metrics_debug: False
• debug: []
• dataloader_drop_last: False
• dataloader_num_workers: 0
• dataloader_prefetch_factor: None
• past_index: -1
• disable_tqdm: False
• remove_unused_columns: True
• label_names: None
• load_best_model_at_end: False
• ignore_data_skip: False
• fsdp: []
• fsdp_min_num_params: 0
• fsdp_config: {'min_num_params': 0, 'xla': False, 'xla_fsdp_v2': False, 'xla_fsdp_grad_ckpt': False}
• fsdp_transformer_layer_cls_to_wrap: None
• accelerator_config: {'split_batches': False, 'dispatch_batches': None, 'even_batches': True, 'use_seedable_sampler': True, 'non_blocking': False, 'gradient_accumulation_kwargs': None}
• deepspeed: None
• label_smoothing_factor: 0.0
• optim: adamw_torch
• optim_args: None
• adafactor: False
• group_by_length: False
• length_column_name: length
• ddp_find_unused_parameters: None
• ddp_bucket_cap_mb: None
• ddp_broadcast_buffers: False
• dataloader_pin_memory: True
• dataloader_persistent_workers: False
• skip_memory_metrics: True
• use_legacy_prediction_loop: False
• push_to_hub: False
• resume_from_checkpoint: None
• hub_model_id: None
• hub_strategy: every_save
• hub_private_repo: None
• hub_always_push: False
• gradient_checkpointing: False
• gradient_checkpointing_kwargs: None
• include_inputs_for_metrics: False
• include_for_metrics: []
• eval_do_concat_batches: True
• fp16_backend: auto
• push_to_hub_model_id: None
• push_to_hub_organization: None
• mp_parameters:
• auto_find_batch_size: False
• full_determinism: False
• torchdynamo: None
• ray_scope: last
• ddp_timeout: 1800
• torch_compile: False
• torch_compile_backend: None
• torch_compile_mode: None
• dispatch_batches: None
• split_batches: None
• include_tokens_per_second: False
• include_num_input_tokens_seen: False
• neftune_noise_alpha: None
• optim_target_modules: None
• batch_eval_metrics: False
• eval_on_start: False
• use_liger_kernel: False
• eval_use_gather_object: False
• average_tokens_across_devices: False
• prompts: None
• batch_sampler: no_duplicates
• multi_dataset_batch_sampler: proportional

</details>

Training Logs

Framework Versions

• Python: 3.10.14
• Sentence Transformers: 3.4.1
• Transformers: 4.49.0
• PyTorch: 2.6.0+cu124
• Accelerate: 1.4.0
• Datasets: 3.3.2
• Tokenizers: 0.21.0

Citation

BibTeX

Sentence Transformers

@inproceedings{reimers-2019-sentence-bert,
    title = "Sentence-BERT: Sentence Embeddings using Siamese BERT-Networks",
    author = "Reimers, Nils and Gurevych, Iryna",
    booktitle = "Proceedings of the 2019 Conference on Empirical Methods in Natural Language Processing",
    month = "11",
    year = "2019",
    publisher = "Association for Computational Linguistics",
    url = "https://arxiv.org/abs/1908.10084",
}

CachedMultipleNegativesRankingLoss

@misc{gao2021scaling,
    title={Scaling Deep Contrastive Learning Batch Size under Memory Limited Setup},
    author={Luyu Gao and Yunyi Zhang and Jiawei Han and Jamie Callan},
    year={2021},
    eprint={2101.06983},
    archivePrefix={arXiv},
    primaryClass={cs.LG}
}

<!-- ## Glossary *Clearly define terms in order to be accessible across audiences.* --> <!-- ## Model Card Authors *Lists the people who create the model card, providing recognition and accountability for the detailed work that goes into its construction.* --> <!-- ## Model Card Contact *Provides a way for people who have updates to the Model Card, suggestions, or questions, to contact the Model Card authors.* -->