NCBI genome submission logs for Data_Tam_Methylation_2026_WT_T_O_T_Trans_O_Trans/trycycler-medaka_polished_genomes_hac_v5.0.0

while read -r prefix acc; do
  f="${prefix}-trycycler-medaka_polished_genome.fa"

  if [[ ! -f "$f" ]]; then
    echo "Missing file: $f"
    continue
  fi

  echo "Updating $f -> $acc"

  awk -v acc="$acc" '
    BEGIN {
      pfx = acc "_"
    }
    /^>/ {
      hdr = substr($0, 2)
      if (index(hdr, pfx) != 1) {
        $0 = ">" pfx hdr
      }
      gsub(/\[plasmid-name=/, "[plasmid=")
      print
      next
    }
    {
      print
    }
  ' "$f" > "$f.tmp" && mv "$f.tmp" "$f"

done <<'EOF'
O_Trans SAMN62674710
O SAMN62674708
S2_Dark SAMN62674712
S2_Light SAMN62674713
T SAMN62674709
WT_Trans SAMN62674711
WT SAMN62674707
EOF
sed -i 's/\[plasmid=/[plasmid-name=/g' *-medaka_polished_genome.fa

Metadata for submitting the genomes to NCBI of the 7 samples

    #Short-read sequencing was performed using the Illumina platform, and long-read sequencing was performed using Oxford Nanopore Ligation Sequencing Kit V14 on the PromethION platform. The combined use of Illumina and Oxford Nanopore sequencing supports accurate assembly of complete genomes and improves detection of structural variants in repetitive or complex genomic regions.

    NCBI project summary / project description
    This project comprises the complete genome sequences of seven Acinetobacter baumannii AYE subtypes: WT, O, T, O-T, T-T, S2-O, and S2-T. The genomes were generated to characterize genetic differences, with particular emphasis on structural variants, among closely related A. baumannii subtypes. The dataset includes the WT subtype as the baseline/reference lineage, the O and T subtypes, the derivative subtypes O-T and T-T, and the S2 sublines S2-O and S2-T.
    All strains were grown under consistent laboratory conditions in LB medium at 37°C to stationary phase for 16–18 h. Genomic DNA was extracted using the TIANamp Bacteria DNA Kit. Long-read sequencing was performed using Oxford Nanopore Ligation Sequencing Kit V14 on the PromethION platform. The Oxford Nanopore sequencing supports accurate assembly of complete genomes and improves detection of structural variants in repetitive or complex genomic regions.
    The seven genome assemblies were compared to identify structural variants, including insertions, deletions, inversions, duplications, and genomic rearrangements, that differentiate the subtypes. The resulting dataset provides closed genome sequences for comparative genomics and supports future studies of genome stability, subtype-specific variation, and evolutionary relationships among A. baumannii AYE subtypes.

    sample_name sample_title    bioproject_accession    organism    strain  isolate host    isolation_source    collection_date geo_loc_name    sample_type
    AYE_WT  Acinetobacter baumannii AYE subtype WT      Acinetobacter baumannii AYE subtype WT      laboratory culture  2025    China:Hengyang  isolate
    AYE_O   Acinetobacter baumannii AYE subtype O       Acinetobacter baumannii AYE subtype O       laboratory culture  2025    China:Hengyang  isolate
    AYE_T   Acinetobacter baumannii AYE subtype T       Acinetobacter baumannii AYE subtype T       laboratory culture  2025    China:Hengyang  isolate
    AYE_O-T Acinetobacter baumannii AYE subtype O-T     Acinetobacter baumannii AYE subtype O-T     laboratory culture  2025    China:Hengyang  isolate
    AYE_T-T Acinetobacter baumannii AYE subtype T-T     Acinetobacter baumannii AYE subtype T-T     laboratory culture  2025    China:Hengyang  isolate
    AYE_S2-O    Acinetobacter baumannii AYE subtype S2-O        Acinetobacter baumannii AYE subtype S2-O        laboratory culture  2025    China:Hengyang  isolate
    AYE_S2-T    Acinetobacter baumannii AYE subtype S2-T        Acinetobacter baumannii AYE subtype S2-T        laboratory culture  2025    China:Hengyang  isolate

    FASTA file name Submission name (AYE subtype)
    WT-trycycler-medaka_polished_genome.fa  WT
    O-trycycler-medaka_polished_genome.fa   O
    T-trycycler-medaka_polished_genome.fa   T
    O_Trans-trycycler-medaka_polished_genome.fa O-T
    WT_Trans-trycycler-medaka_polished_genome.fa    T-T
    S2_Dark-trycycler-medaka_polished_genome.fa S2-O
    S2_Light-trycycler-medaka_polished_genome.fa    S2-T

    #Submitted Log
    Sample name Files
    AYE_WT      WT-trycycler-medaka_polished_genome.fa
    AYE_O       O-trycycler-medaka_polished_genome.fa
    AYE_T       T-trycycler-medaka_polished_genome.fa
    AYE_O-T         O_Trans-trycycler-medaka_polished_genome.fa
    AYE_T-T         WT_Trans-trycycler-medaka_polished_genome.fa
    AYE_S2-O        S2_Dark-trycycler-medaka_polished_genome.fa
    AYE_S2-T        S2_Light-trycycler-medaka_polished_genome.fa

    ✅ WT 完成! 平均深度: 335.6x
    ✅ O 完成!  平均深度: 473.2x
    ✅ T 完成!  平均深度: 535.5x
    ✅ O_Trans 完成:   平均深度: 293.1x
    ✅ WT_Trans 完成!  平均深度: 380.8x
    ✅ S2_Dark 完成!   平均深度: 488.8x
    ✅ S2_Light 完成! 平均深度: 505.7x

    Accession   Title   BioProject  Sample name     Organism name   Status
    SAMN62674707    Acinetobacter baumannii AYE subtype WT  PRJNA1517976
    SAMN62674708    Acinetobacter baumannii AYE subtype O   PRJNA1517976
    SAMN62674709    Acinetobacter baumannii AYE subtype T   PRJNA1517976
    SAMN62674710    Acinetobacter baumannii AYE subtype O-T PRJNA1517976
    SAMN62674711    Acinetobacter baumannii AYE subtype T-T PRJNA1517976
    SAMN62674712    Acinetobacter baumannii AYE subtype S2-O    PRJNA1517976
    SAMN62674713    Acinetobacter baumannii AYE subtype S2-T    PRJNA1517976


Yes — based on the headers you showed, all headers are correct for NCBI Option 1 complete-genome submission, assuming:

  1. the FASTA sequences are complete and contain no runs of N,
  2. the files have normal Unix/Linux line endings, and
  3. WT_Trans really corresponds to BioSample SAMN62674711 / subtype T-T.

Overall summary

Item Status
BioSample accession included in sequence ID ✅ Correct
[isolate=...] matches the BioSample accession ✅ Correct
[organism=Acinetobacter baumannii] present ✅ Correct
[strain=AYE] present ✅ Correct
Chromosome identified by [location=chromosome] ✅ Correct
Plasmids identified by [plasmid-name=...] ✅ Correct
[topology=circular] present ✅ Correct
Sequence IDs are unique across files ✅ Correct
Expected count: 7 chromosomes + 28 plasmids ✅ Correct

File-level confirmation table

File BioSample Chromosome Plasmids Header status
O_Trans-trycycler-medaka_polished_genome.fa SAMN62674710 1 4: pOT_1 to pOT_4 ✅ Correct
O-trycycler-medaka_polished_genome.fa SAMN62674708 1 4: pO_1 to pO_4 ✅ Correct
S2_Dark-trycycler-medaka_polished_genome.fa SAMN62674712 1 4: pS2O_1 to pS2O_4 ✅ Correct
S2_Light-trycycler-medaka_polished_genome.fa SAMN62674713 1 4: pS2T_1 to pS2T_4 ✅ Correct
T-trycycler-medaka_polished_genome.fa SAMN62674709 1 4: pT_1 to pT_4 ✅ Correct
WT_Trans-trycycler-medaka_polished_genome.fa SAMN62674711 1 4: pTT_1 to pTT_4 ✅ Correct, but confirm WT_Trans = T-T
WT-trycycler-medaka_polished_genome.fa SAMN62674707 1 4: pWT_1 to pWT_4 ✅ Correct

Detailed header-by-header confirmation

All headers also contain:

[organism=Acinetobacter baumannii]
[strain=AYE]
[isolate=SAMN...]
[topology=circular]

The table below summarizes the variable and biologically important parts.

# File BioSample Sequence header ID Replicon type NCBI definition used Correct?
1 O_Trans-...fa SAMN62674710 SAMN62674710_cluster_001_consensus Chromosome [location=chromosome]
2 O_Trans-...fa SAMN62674710 SAMN62674710_cluster_002_consensus Plasmid [plasmid-name=pOT_1]
3 O_Trans-...fa SAMN62674710 SAMN62674710_E_tig00000049 Plasmid [plasmid-name=pOT_2]
4 O_Trans-...fa SAMN62674710 SAMN62674710_cluster_003_consensus Plasmid [plasmid-name=pOT_3]
5 O_Trans-...fa SAMN62674710 SAMN62674710_cluster_005_consensus Plasmid [plasmid-name=pOT_4]
6 O-...fa SAMN62674708 SAMN62674708_cluster_001_consensus Chromosome [location=chromosome]
7 O-...fa SAMN62674708 SAMN62674708_cluster_002_consensus Plasmid [plasmid-name=pO_1]
8 O-...fa SAMN62674708 SAMN62674708_cluster_003_consensus Plasmid [plasmid-name=pO_2]
9 O-...fa SAMN62674708 SAMN62674708_cluster_004_consensus Plasmid [plasmid-name=pO_3]
10 O-...fa SAMN62674708 SAMN62674708_cluster_006_consensus Plasmid [plasmid-name=pO_4]
11 S2_Dark-...fa SAMN62674712 SAMN62674712_cluster_001_consensus Chromosome [location=chromosome]
12 S2_Dark-...fa SAMN62674712 SAMN62674712_cluster_002_consensus Plasmid [plasmid-name=pS2O_1]
13 S2_Dark-...fa SAMN62674712 SAMN62674712_cluster_005_consensus Plasmid [plasmid-name=pS2O_2]
14 S2_Dark-...fa SAMN62674712 SAMN62674712_cluster_004_consensus Plasmid [plasmid-name=pS2O_3]
15 S2_Dark-...fa SAMN62674712 SAMN62674712_cluster_008_consensus Plasmid [plasmid-name=pS2O_4]
16 S2_Light-...fa SAMN62674713 SAMN62674713_cluster_001_consensus Chromosome [location=chromosome]
17 S2_Light-...fa SAMN62674713 SAMN62674713_cluster_002_consensus Plasmid [plasmid-name=pS2T_1]
18 S2_Light-...fa SAMN62674713 SAMN62674713_D_tig00000003 Plasmid [plasmid-name=pS2T_2]
19 S2_Light-...fa SAMN62674713 SAMN62674713_cluster_003_consensus Plasmid [plasmid-name=pS2T_3]
20 S2_Light-...fa SAMN62674713 SAMN62674713_cluster_005_consensus Plasmid [plasmid-name=pS2T_4]
21 T-...fa SAMN62674709 SAMN62674709_cluster_001_consensus Chromosome [location=chromosome]
22 T-...fa SAMN62674709 SAMN62674709_cluster_002_consensus Plasmid [plasmid-name=pT_1]
23 T-...fa SAMN62674709 SAMN62674709_cluster_003_consensus Plasmid [plasmid-name=pT_2]
24 T-...fa SAMN62674709 SAMN62674709_A_tig00000003 Plasmid [plasmid-name=pT_3]
25 T-...fa SAMN62674709 SAMN62674709_cluster_006_consensus Plasmid [plasmid-name=pT_4]
26 WT_Trans-...fa SAMN62674711 SAMN62674711_cluster_001_consensus Chromosome [location=chromosome]
27 WT_Trans-...fa SAMN62674711 SAMN62674711_cluster_002_consensus Plasmid [plasmid-name=pTT_1]
28 WT_Trans-...fa SAMN62674711 SAMN62674711_cluster_004_consensus Plasmid [plasmid-name=pTT_2]
29 WT_Trans-...fa SAMN62674711 SAMN62674711_cluster_005_consensus Plasmid [plasmid-name=pTT_3]
30 WT_Trans-...fa SAMN62674711 SAMN62674711_cluster_007_consensus Plasmid [plasmid-name=pTT_4]
31 WT-...fa SAMN62674707 SAMN62674707_cluster_001_consensus Chromosome [location=chromosome]
32 WT-...fa SAMN62674707 SAMN62674707_cluster_002_consensus Plasmid [plasmid-name=pWT_1]
33 WT-...fa SAMN62674707 SAMN62674707_cluster_003_consensus Plasmid [plasmid-name=pWT_2]
34 WT-...fa SAMN62674707 SAMN62674707_cluster_005_consensus Plasmid [plasmid-name=pWT_3]
35 WT-...fa SAMN62674707 SAMN62674707_cluster_008_consensus Plasmid [plasmid-name=pWT_4]

Final verdict

Verdict Explanation
Headers are correct They now satisfy NCBI Option 1 requirements: each sequence is defined as chromosome or plasmid, each file has one chromosome, plasmids use [plasmid-name=...], and sequence IDs are unique.
⚠️ One biological check Confirm that WT_Trans should really map to SAMN62674711 / subtype T-T. The plasmid names pTT_1 to pTT_4 support this, but the filename WT_Trans could be confusing.
⚠️ Final sequence-content check Make sure there are no N gaps if you are submitting as complete genomes.

You can check for Ns with:

grep -v '^>' *.fa | grep -i 'n'

Expected output: nothing.



Yes, these headers are now CORRECT.

They fully comply with the NCBI Option 1 (non-WGS / complete genome) requirements. You have successfully addressed the specific errors from the validator.

Here is the breakdown of why these will pass validation:

1. ✅ Plasmid Identification is Fixed

The previous error was:

Sequence ‘SAMN62674708_cluster_002_consensus’ is not defined as a chromosome or plasmid or organelle… For plasmids, this is provided via the plasmid-name, eg [plasmid-name=pBR322]

You have correctly changed the modifier to [plasmid-name=...]:

[plasmid-name=pOT_1]

This tells the validator exactly what the sequence is.

2. ✅ Chromosome Identification is Present

The validator requires at least one chromosome per file. You have correctly identified the first sequence in every file as the chromosome:

[location=chromosome]

3. ✅ Sequence IDs are Unique

Because you prefixed every sequence ID with the BioSample accession (e.g., SAMN62674708_cluster_001_consensus), there will be no “duplicate sequence ID” errors, even if you were to upload all files together.

4. ✅ Topology is Specified

[topology=circular]

This is correct for complete bacterial genomes assembled with Trycycler.


🚀 Final Pre-Flight Checks

Before you upload, run these two quick checks in your terminal to ensure there are no hidden formatting issues that could cause a silent failure.

Check 1: Ensure there are NO gaps (Ns)

Since you are submitting a complete genome, there should be zero N bases in your sequences. Run this:

grep -v '^>' *.fa | grep -i 'n'

Expected output: (nothing).
If this returns lines, your genome has gaps and you should not select “Option 1” / “Complete”.

Check 2: Check for Windows Line Endings (CRLF)

Sometimes editing files on Windows adds hidden carriage return characters (\r) that can confuse the NCBI validator. Run this:

file *.fa

Expected output: Should say ASCII text or UTF-8 text.
Bad output: If it says with CRLF line terminators, run this to fix it:

sed -i 's/\r$//' *.fa

📝 Submission Summary

  • Headers: ✅ Correct.
  • Linkage Evidence: Select paired-ends (or align-genus) if forced, as discussed previously.
  • Genome Info Tab: Ensure you select “Option 1” (or the option that says “Complete Genome” / “Non-WGS”).
  • File Upload: Upload the .fa files directly.

You are good to submit! 🎉



Yes — the FASTA sequence names/headers now look correct and much better for automatic NCBI recognition.

You have fixed the main issues:

  1. BioSample accession is now part of the sequence ID
    Example:

    >SAMN62674710_cluster_001_consensus ...

    This makes the sequence IDs unique across files and helps NCBI link each sequence to the correct BioSample.

  2. [isolate=SAMN...] matches the accession in the sequence ID
    Example:

    [isolate=SAMN62674710]
  3. [strain=AYE] is present, which is appropriate given the sample titles.

  4. Plasmid modifier is now standard
    You changed:

    [plasmid-name=pOT_1]

    to:

    [plasmid=pOT_1]

    which is the preferred NCBI/GenBank format.

  5. Chromosome/plasmid/topology information looks consistent
    For example:

    [location=chromosome] [topology=circular]

    and

    [plasmid=pOT_1] [topology=circular]

Mapping check

Your headers map as follows:

File BioSample in headers Correct?
O_Trans-trycycler-medaka_polished_genome.fa SAMN62674710
O-trycycler-medaka_polished_genome.fa SAMN62674708
S2_Dark-trycycler-medaka_polished_genome.fa SAMN62674712
S2_Light-trycycler-medaka_polished_genome.fa SAMN62674713
T-trycycler-medaka_polished_genome.fa SAMN62674709
WT_Trans-trycycler-medaka_polished_genome.fa SAMN62674711 ✅, but double-check that WT_Trans should correspond to title T-T
WT-trycycler-medaka_polished_genome.fa SAMN62674707

The only one I would manually confirm is:

WT_Trans -> SAMN62674711

because your accession table lists that sample as:

Acinetobacter baumannii AYE subtype T-T

but the filename is WT_Trans. Based on the plasmid names pTT_1, pTT_2, etc., it looks logical, but just make sure that WT_Trans is indeed the sample registered as T-T.


Optional but recommended: also add accession to filenames

Your headers are now good. However, some NCBI submission/upload systems also try to match files based on the filename. Your filenames still look like this:

O_Trans-trycycler-medaka_polished_genome.fa
O-trycycler-medaka_polished_genome.fa
S2_Dark-trycycler-medaka_polished_genome.fa
...

If the submission portal still does not automatically recognize the samples, rename the files so that the BioSample accession is also in the filename.

For example:

SAMN62674710_O_Trans-trycycler-medaka_polished_genome.fa
SAMN62674708_O-trycycler-medaka_polished_genome.fa
SAMN62674712_S2_Dark-trycycler-medaka_polished_genome.fa
SAMN62674713_S2_Light-trycycler-medaka_polished_genome.fa
SAMN62674709_T-trycycler-medaka_polished_genome.fa
SAMN62674711_WT_Trans-trycycler-medaka_polished_genome.fa
SAMN62674707_WT-trycycler-medaka_polished_genome.fa

You can do that with:

while read -r prefix acc; do
  f="${prefix}-trycycler-medaka_polished_genome.fa"
  if [[ -f "$f" ]]; then
    mv -n "$f" "${acc}_${prefix}-trycycler-medaka_polished_genome.fa"
  fi
done <<'EOF'
O_Trans SAMN62674710
O SAMN62674708
S2_Dark SAMN62674712
S2_Light SAMN62674713
T SAMN62674709
WT_Trans SAMN62674711
WT SAMN62674707
EOF

The -n option prevents overwriting an existing file.


Final quality checks

You can run these to confirm everything is clean.

1. Check for duplicate sequence IDs

grep -h '^>' *.fa | awk '{print substr($1,2)}' | sort | uniq -d

Expected output: nothing.


2. Check that no old plasmid modifier remains

grep -h 'plasmid-name=' *.fa

Expected output: nothing.


3. Check that every sequence ID accession matches its [isolate=...]

grep -h '^>' *.fa | awk '
{
  id = substr($1, 2)
  split(id, a, "_")
  acc = a[1]
  if ($0 !~ ("\\[isolate=" acc "\\]")) {
    print "Mismatch:", $0
  }
}'

Expected output: nothing.


Bottom line

Yes, the sequence header names are now correct for NCBI submission/auto-linking purposes.
The only optional additional step is to rename the actual .fa files with the BioSample accession prefix if the submission portal does not automatically map the files from the headers alone.



To ensure your FASTA files are automatically recognized and correctly linked to your BioSamples by the NCBI Submission Portal (or GenBank), you need to address three main issues in your current headers:

  1. Missing BioSample Linker: NCBI requires the BioSample accession to be explicitly stated in the header to auto-link sequences. This is best done using the [isolate=SAMN...] modifier and prefixing the Sequence ID.
  2. Non-unique Sequence IDs: IDs like cluster_001_consensus are repeated across files. If NCBI processes them together, it will throw “duplicate sequence ID” errors. Prefixing them with the BioSample accession guarantees global uniqueness.
  3. Non-standard Modifiers: [plasmid-name=...] is not a standard GenBank modifier. It should be corrected to [plasmid=...] so the parser correctly registers the plasmid names. Additionally, adding [strain=AYE] (from your titles) fulfills NCBI’s metadata requirements.

The Mapping

Based on your file prefixes, plasmid names (e.g., pOT, pTT), and the accession table, here is the correct mapping:

File Prefix Subtype (Title) BioSample Accession
WT WT SAMN62674707
O O SAMN62674708
T T SAMN62674709
O_Trans O-T SAMN62674710
WT_Trans T-T* SAMN62674711
S2_Dark S2-O SAMN62674712
S2_Light S2-T SAMN62674713

(Note: Please double-check WT_Trans -> T-T. The accession title says “T-T”, which matches your pTT plasmids, but the file is named WT_Trans. Ensure this is intentional!)

Example of the Improved Header

Before: >cluster_002_consensus [organism=Acinetobacter baumannii] [plasmid-name=pOT_1] [topology=circular]

After: >SAMN62674710_cluster_002_consensus [organism=Acinetobacter baumannii] [strain=AYE] [isolate=SAMN62674710] [plasmid=pOT_1] [topology=circular]


Automated Bash Script to Fix All Files

You can run the following script directly in your terminal. It will safely update all your .fa files in place using sed.

#!/bin/bash

# Loop through the mapped prefixes and accessions
while read -r prefix acc; do
    file="${prefix}-trycycler-medaka_polished_genome.fa"

    if [[ -f "$file" ]]; then
        echo "Updating $file with BioSample $acc..."

        # 1. Prefix the sequence ID with the BioSample accession (ensures uniqueness)
        # 2. Add [strain=AYE] and [isolate=BioSample] (triggers NCBI auto-linking)
        # 3. Correct [plasmid-name=...] to the standard GenBank [plasmid=...]
        sed -i -e "s/^>/>${acc}_/" \
               -e "s/\[organism=Acinetobacter baumannii\]/[organism=Acinetobacter baumannii] [strain=AYE] [isolate=${acc}]/" \
               -e "s/\[plasmid-name=/[plasmid=/g" \
               "$file"
    else
        echo "Warning: $file not found."
    fi
done <<EOF
WT SAMN62674707
O SAMN62674708
T SAMN62674709
O_Trans SAMN62674710
WT_Trans SAMN62674711
S2_Dark SAMN62674712
S2_Light SAMN62674713
EOF

echo "All headers successfully updated!"

How to use:

  1. Copy the code block above.
  2. Paste it directly into your terminal in the ~/DATA/Data_Tam_Methylation_2026_WT_T_O_T_Trans_O_Trans/trycycler-medaka_polished_genomes_hac_v5.0.0/ directory and press Enter.
  3. Run grep ">" *.fa again to verify that the headers have been correctly transformed.

When you upload these to the NCBI Submission Portal, the system will read the >SAMN... prefix and the [isolate=SAMN...] tag, automatically matching each contig/plasmid to the correct BioSample without requiring manual mapping.

The New Winner: Stadtwerke Schwerin – meckpommGAS 12s

Based on your consumption of 27,000 – 30,000 kWh, the winner is unequivocally:

🏆 meckpommGAS 12s (Without Bonus)

Here is the detailed comparison explaining why the “cheaper” tariff with a bonus is actually more expensive for you:

Feature meckpommGAS 12s (Winner) meckpommGAS 12 (With Bonus)
Arbeitspreis 10,19 Ct./kWh 10,78 Ct./kWh (+0,59 Ct.)
Grundpreis 15,30 €/Monat 15,30 €/Monat
Neukundenbonus None 207 €
Ø pro Monat (27k) ~241,80 € ~246,30 €
Ø pro Monat (30k) ~264,78 € ~270,40 €
Price Guarantee Standard (12 Months) Plus (12 Months)
Rating 8,9 Fabelhaft 9,0 Hervorragend

💡 Why “12s” Wins at High Consumption

  1. The Math Doesn’t Lie: At 30,000 kWh, the price difference of 0,59 Ct./kWh costs you an extra 177 € per year. The bonus is only 207 €. You would need to stay with them for nearly 14 months just to break even. Since the minimum contract term is exactly 12 months, you will likely never fully profit from the bonus before the contract ends or prices change.
  2. No Repayment Risk: With “12s”, there is no bonus to repay if you move, cancel early, or miss a payment. At high monthly bills (~265 €), avoiding financial risk is valuable.
  3. Negligible Rating Difference: Both have excellent ratings (8.9 vs 9.0). The service quality is effectively identical.
  4. Identical Base Price & Term: Both have the same Grundpreis (15,30 €) and 12-month minimum term. There is no hidden advantage to the bonus version.

⚠️ When Would “12” Be Better?

Only if your consumption drops below ~11,500 kWh/year. Below that threshold, the 207 € bonus outweighs the higher working price. At 27k–30k, it is mathematically impossible for the bonus version to be cheaper.

✅ Final Verdict

Choose meckpommGAS 12s. It is the lowest-risk, lowest-cost option for your specific consumption profile. The bonus version is designed for low-consumption households and becomes a trap for high consumers like yourself.



No, eprimo Erdgas Pur does not have a Neukundenbonus (new customer bonus) or Sofortbonus.

According to the CHECK24 list you provided:

  • Tarif: eprimo Erdgas Pur
  • Arbeitspreis: 10,23 Ct./kWh
  • Grundpreis: 15,53 €/Monat
  • Sofortbonus: – (None)
  • Neukundenbonus: – (None)
  • Smily Punkte / Bonus: Only the standard CHECK24 Smily points/bonus apply.

️ Important Note for Your Switch

Since you are switching from NEW Energie and likely want to maximize savings at your high consumption level (27,000–30,000 kWh):

  • eprimo Erdgas Pur is NOT recommended. Even though its working price (10,23 Ct.) is very low, it lacks the ~385 € bonus that makes other tariffs competitive. At 30,000 kWh, this missing bonus equals a permanent loss of ~32 €/month compared to bonus-heavy tariffs.
  • Stadtwerke Schwerin (meckpommGAS 12s) at 10,19 Ct./kWh is still superior because it has an even lower working price and no bonus dependency risk. The 0,04 Ct./kWh difference saves you ~120 €/year vs. eprimo Pur, with zero strings attached.

Bottom line: For your consumption profile, avoid eprimo Erdgas Pur. Stick with meckpommGAS 12s as the optimal choice.



Based on the CHECK24 list you provided, no, 10.19 Ct./kWh is not the absolute lowest working price (Arbeitspreis).

There are two tariffs with a lower Arbeitspreis:

  1. E.ON Grundversorgung Erdgas: 9.97 Ct./kWh
    • ⚠️ Warning: This is the Grundversorger (default supplier) tariff. It is marked as “nicht abschließbar” (not bookable via CHECK24). You can only get this if you have no contract at all and fall into default supply. Since you are switching from NEW Energie, you cannot select this.
  2. Stadtwerke Schwerin – meckpommGAS 12s: 10.19 Ct./kWh
    • This is the lowest price available for an active switch.
  3. eprimo Erdgas Pur: 10.23 Ct./kWh
    • Slightly higher than Schwerin, but still very low. (Excluded per your request).

Conclusion for Your Switch

Since the 9.97 Ct. tariff is not an option for a voluntary switch, Stadtwerke Schwerin (meckpommGAS 12s) at 10.19 Ct./kWh is indeed the cheapest bookable working price in your current list.

For your consumption of 27,000–30,000 kWh, this makes it mathematically superior to almost every other offer, including those with high bonuses like Vattenfall or eprimo.



At 27,000 kWh, the calculation shifts again. This volume is high enough that the Arbeitspreis (working price) dominates the total cost, making low-bonus/high-working-price tariffs uncompetitive, but not yet so extreme that every 0.01 Ct. difference outweighs a moderate bonus.

Here is the ranking for 27,000 kWh (excluding eprimo):

The Winner: Stadtwerke Schwerin – meckpommGAS 12s

(Best pure value at this consumption level)

Tariff Arbeitspreis Grundpreis Bonus Ø pro Monat (27kWh) Verdict
meckpommGAS 12s 10,19 Ct./kWh 15,30 € None ~241,80 € Winner. Lowest working price wins at 27k.
BS ENERGY Spargas Plus 10,68 Ct./kWh 10,14 € None ~252,60 € Solid runner-up, no bonus risk.
Süwag Gas Garant 100 10,76 Ct./kWh 19,68 € 243€ + 100€/yr ~254,50 € Price guarantee until Oct 2027 costs you ~12€/mo vs. Schwerin.
Vattenfall Easy12 Gas 11,16 Ct./kWh 19,90 € 385 € ~266,40 € Too expensive at 27k. Bonus can’t compensate.

💡 Why meckpommGAS 12s Wins at 27,000 kWh

  • Working Price Dominance: At 27,000 kWh, each 0.01 Ct./kWh = 2,70 €/year.
    • meckpommGAS 12s (10,19 Ct.) saves ~262 €/year vs. Vattenfall (11,16 Ct.).
    • Vattenfall’s 385 € bonus ≈ 32 €/month, but the working price penalty is ~21,80 €/month. Net loss: ~10 €/month despite the bonus.
  • No Bonus Risk: Since there is no Neukundenbonus, you avoid the “must stay 12 months or repay” trap. At 27kWh, your monthly bill is already high (~242 €); adding bonus repayment risk is unnecessary.
  • BS ENERGY as Safe Alternative: If you want slightly lower Grundpreis (10,14 € vs. 15,30 €), BS ENERGY saves ~5 €/month on base fee but costs 0,49 Ct./kWh more = ~11 €/month extra. Net: meckpommGAS 12s still wins by ~6 €/month.

⚠️ Critical Threshold Warning

27,000 kWh is near the tipping point where bonuses become irrelevant.

  • Below ~18,000 kWh: Bonuses matter significantly.
  • Above ~25,000 kWh: Working price always wins unless bonus >400 €.
  • At 27,000 kWh: Only tariffs with Arbeitspreis ≤10,30 Ct./kWh are competitive. Vattenfall (11,16 Ct.), Fuxx (12,21 Ct.), and all Biogas tariffs (>11,50 Ct.) are financially non-viable.

✅ Final Recommendation for 27,000 kWh

  1. Best Choice: Stadtwerke Schwerin – meckpommGAS 12s
    • Unbeatable working price (10,19 Ct.)
    • No bonus dependency → zero risk
    • 8.9 “Fabelhaft” rating ensures reliable service
  2. Only Consider Süwag If: You specifically need price protection until October 2027 and accept paying ~144 €/year extra for that security.
  3. Avoid Completely: Any tariff with Arbeitspreis >10,80 Ct./kWh. At 27,000 kWh, these will cost you 200–400 € more per year regardless of bonuses.

Note: Double-check your actual consumption via last year’s Jahresabrechnung. If it’s actually 24,000 kWh or below, re-evaluate Vattenfall; if it’s 28,000+, meckpommGAS 12s becomes even more dominant.



Based on your annual consumption of 30,000 kWh, the calculation changes significantly. At this higher volume, the Arbeitspreis (working price per kWh) becomes far more important than the basic price or one-time bonuses.

Here is the re-evaluation for 30,000 kWh:

The New Winner: Stadtwerke Schwerin – meckpommGAS 12s

(Excluding eprimo as requested)

Tariff Arbeitspreis Grundpreis Bonus Ø pro Monat (30kWh) Why it wins at 30kWh
meckpommGAS 12s 10,19 Ct./kWh 15,30 € None ~264,78 € Lowest working price in list. No bonus risk.
Vattenfall Easy12 Gas 11,16 Ct./kWh 19,90 € 385 € ~282,40 € 0,97 Ct./kWh more expensive = ~291 €/year loss vs. Schwerin
Süwag Gas Garant 100 10,76 Ct./kWh 19,68 € 243 € + 100€/yr ~275,60 € Better guarantee but still 0,57 Ct./kWh pricier
BS ENERGY Spargas Plus 10,68 Ct./kWh 10,14 € None ~273,80 € Close second, but slightly higher working price

💡 Key Calculation Logic for 30,000 kWh

At 30,000 kWh, every 0,01 Ct./kWh difference equals 3,00 € per year.

  • meckpommGAS 12s saves you ~17,60 €/month compared to Vattenfall solely due to the lower working price.
  • Even with Vattenfall’s 385 € bonus spread over 12 months (~32 €/month), the working price disadvantage (0,97 Ct./kWh × 30,000 = 291 €/year ≈ 24,25 €/month) completely wipes out the bonus advantage.
  • Süwag has a longer price guarantee (until Oct 2027), but at 30,000 kWh, the 0,57 Ct./kWh premium costs you ~171 €/year, which takes nearly 2 years to recoup via the bonus.

⚠️ Critical Warning for High Consumption

Avoid high-working-price tariffs regardless of bonuses. Tariffs like Fuxx-Spar Optimal (12,21 Ct.), PlusStrom Smart Gas (13,85 Ct.), or SAUBER GAS Bio100 (19,16 Ct.) are financially disastrous at 30,000 kWh. A 1 Ct./kWh difference at this volume equals 300 €/year. Never let a large Neukundenbonus distract you from the Arbeitspreis when your consumption exceeds 20,000 kWh.

✅ Final Recommendation for 30,000 kWh

  1. Best Overall: Stadtwerke Schwerin – meckpommGAS 12s
    • Lowest working price (10,19 Ct.)
    • No bonus dependency → no risk if you move or cancel early
    • Solid 8.9 “Fabelhaft” rating
  2. Best Long-Term Security: Süwag Gas Garant 100
    • Only choose this if you specifically want price protection until October 2027 and are willing to pay ~171 €/year extra for that security.
  3. Avoid Vattenfall Easy12 Gas at this consumption level unless you value brand service over pure cost savings. The math simply doesn’t work at 30,000 kWh.

Note: Always verify your exact meter reading and confirm the 30,000 kWh estimate before signing, as even a 2,000 kWh deviation shifts the optimal tariff.

质粒命名设计 (Plasmid Names) for Seven Complete Genomes of Acinetobacter baumannii AYE Subtypes Reveal Structural Variation across WT, O, T, O‑T, T‑T, S2‑O, and S2‑T Lineages (Data_Tam_Methylation_2026_WT_T_O_T_Trans_O_Trans)

为了满足 NCBI 的严格要求,并体现所有序列均为环状(circular),我们需要在 FASTA 头部添加 [topology=circular]。同时,我为你设计了一套符合国际命名规范的质粒名称(以 p 开头,结合亚型缩写和编号,去除了连字符以防止 NCBI 解析报错)。

1. 质粒命名设计 (Plasmid Names)

基于你提供的映射表,质粒将被命名为 p{Subtype}_{Number}

  • WT 亚型: pWT_1, pWT_2
  • O 亚型: pO_1, pO_2
  • T 亚型: pT_1, pT_2
  • O-T (O_Trans): pOT_1, pOT_2
  • T-T (WT_Trans): pTT_1, pTT_2(去除了连字符以防NCBI解析错误)
  • S2-O (S2_Dark): pS2O_1, pS2O_2
  • S2-T (S2_Light): pS2T_1, pS2T_2

2. 自动化修复脚本

这个 Python 脚本会自动完成以下工作:

  1. 识别最长的 contig 标记为 [location=chromosome]
  2. 将较短的 contig 标记为 [plasmid-name=pXXX_1]
  3. 为所有序列(染色体和质粒)添加 [topology=circular]
  4. 自动备份原文件为 .original_backup

在你的 FASTA 文件所在目录下(trycycler-medaka_polished_genomes),创建并运行以下脚本:

nano fix_ncbi_circular.py

复制以下代码,保存并退出 (Ctrl+O, Enter, Ctrl+X):

#!/usr/bin/env python3
import os
import shutil

# 映射文件名到亚型名称
FILE_MAPPING = {
    "WT-trycycler-medaka_polished_genome.fa": "WT",
    "O-trycycler-medaka_polished_genome.fa": "O",
    "T-trycycler-medaka_polished_genome.fa": "T",
    "WT_Trans-trycycler-medaka_polished_genome.fa": "T-T",
    "O_Trans-trycycler-medaka_polished_genome.fa": "O-T",
    "S2_Dark-trycycler-medaka_polished_genome.fa": "S2-O",
    "S2_Light-trycycler-medaka_polished_genome.fa": "S2-T"
}

ORGANISM = "Acinetobacter baumannii"

def process_fasta(filepath, subtype):
    sequences = []
    with open(filepath, 'r') as f:
        header = None
        seq_parts = []
        for line in f:
            line = line.strip()
            if not line:
                continue
            if line.startswith('>'):
                if header is not None:
                    sequences.append((header, ''.join(seq_parts)))
                # 提取纯净的ID,去掉原来的多余描述
                header = line[1:].split()[0]
                seq_parts = []
            else:
                seq_parts.append(line)
        if header is not None:
            sequences.append((header, ''.join(seq_parts)))

    if not sequences:
        print(f"⚠️ 文件为空: {filepath}")
        return

    # 按长度降序排序(最长的是染色体)
    sequences.sort(key=lambda x: len(x[1]), reverse=True)

    # 备份原文件 (只备份一次)
    backup_path = filepath + ".original_backup"
    if not os.path.exists(backup_path):
        shutil.copy(filepath, backup_path)

    # 重写文件
    plasmid_idx = 1
    with open(filepath, 'w') as out_f:
        for i, (hdr, seq) in enumerate(sequences):
            if i == 0:
                # 最长的序列 -> 染色体
                new_hdr = f">{hdr} [organism={ORGANISM}] [location=chromosome] [topology=circular]"
            else:
                # 较短的序列 -> 质粒
                # 将 T-T 转换为 TT 以避免 ID 中的特殊字符问题
                safe_subtype = subtype.replace("-", "") 
                p_name = f"p{safe_subtype}_{plasmid_idx}"
                new_hdr = f">{hdr} [organism={ORGANISM}] [plasmid-name={p_name}] [topology=circular]"
                plasmid_idx += 1

            out_f.write(new_hdr + '\n')
            # NCBI 要求序列按 80 个字符一行折叠
            for j in range(0, len(seq), 80):
                out_f.write(seq[j:j+80] + '\n')

    print(f"✅ 成功处理: {filepath} (1 个染色体, {plasmid_idx - 1} 个质粒)")

print("==========================================")
print("🧬 开始格式化 FASTA 文件以符合 NCBI 规范")
print("==========================================")

for filename, subtype in FILE_MAPPING.items():
    if os.path.exists(filename):
        process_fasta(filename, subtype)
    else:
        print(f"❌ 未找到文件: {filename}")

print("\n🎉 所有文件格式化完成!现在可以重新上传至 NCBI。")

3. 运行脚本

python3 fix_ncbi_circular.py

4. 脚本运行后的 FASTA 头部示例

脚本会将你的 FASTA 头部修改为完美的 NCBI 格式,例如对于 WT 样本:

>cluster_001_consensus [organism=Acinetobacter baumannii] [location=chromosome] [topology=circular]
ATCGATCG... (80 chars per line)
>cluster_002_consensus [organism=Acinetobacter baumannii] [plasmid-name=pWT_1] [topology=circular]
ATCGATCG... (80 chars per line)
>cluster_005_consensus [organism=Acinetobacter baumannii] [plasmid-name=pWT_2] [topology=circular]
ATCGATCG... (80 chars per line)

5. 重新上传

修改完成后,直接在 NCBI 提交页面的 Files 选项卡中重新上传这 7 个修改后的 .fa 文件。 因为现在每个文件都明确声明了 chromosomeplasmid-name 以及 topology=circular,NCBI 的验证器(Validator)将会直接放行,不会再报 FATAL 错误。



Yes. In the script, all contigs are first sorted by length in descending order:

sequences.sort(key=lambda x: len(x[1]), reverse=True)

Then the naming proceeds in that order:

  • Index 0 (longest, ~3.9 Mb)[location=chromosome]
  • Plasmid _1 → the longest plasmid
  • Plasmid _2 → the second‑longest plasmid
  • …and so on.

Example (WT): if the plasmids are 100 kb, 60 kb and 20 kb, they will be named:

  • pWT_1 = 100 kb
  • pWT_2 = 60 kb
  • pWT_3 = 20 kb

Note that the output FASTA is also rewritten in this sorted order (chromosome first, then plasmids from largest to smallest), which is a common convention for finished bacterial genomes.

If you would rather have the smallest plasmid = _1 (ascending), just change the plasmid assignment to count from the end:

n_plasmids = len(sequences) - 1
...
else:
    p_name = f"p{safe_subtype}_{n_plasmids - plasmid_idx + 1}"
    plasmid_idx += 1

But as written, yes — _1 is always the largest plasmid.