bodyType

customContents

entityId

printArticlePageQuery

filter

article

body

urlAlias

articleSectionsContent

articleSeoArticle

articleSourceHeaderArticle

contentSchemaRenderContent

contentSubHeadlineContent

contentHeadlineContent

mainImagePrintArticleArticle

authorBlockPrintArticleArticle

contentSponsorTagContent

articlePianoPaywallContent

scmpYoutubeContent

hooksTrackPageViewArticle

query printArticlePageQuery(
  $entityId: String!
  $customContents: [CustomContentInput]
  $bodyType: BodyFormatTypeEnum
) {
  article(filter: {entityId: $entityId}) {
    entityId
    body(customContents: $customContents, type: $bodyType) {
      json
    }
    urlAlias
    ...articleSectionsContent
    ...articleSeoArticle_3o8td4
    ...articleSourceHeaderArticle
    ...contentSchemaRenderContent
    ...contentSubHeadlineContent
    ...contentHeadlineContent
    ...mainImagePrintArticleArticle
    ...authorBlockPrintArticleArticle
    ...contentSponsorTagContent
    ...articlePianoPaywallContent
    ...scmpYoutubeContent
    ...hooksTrackPageViewArticle
    id
  }
}

fragment articlePianoPaywallContent on Content {
  __isContent: __typename
  ...hooksPaywallPromiseContent
}

fragment articleSectionsContent on Content {
  __isContent: __typename
  sections {
    value {
      ...helpersCheckIfNewsSectionInFirstIndexSection
      ...entityLink
      name
      id
    }
  }
}

fragment articleSeoArticle_3o8td4 on Article {
  ...hooksArticleSeoArticle
  ...helpersCheckIsPostiesArticle
  ...helpersGetArticleTypeArticle
  entityId
  publishedDate
  updatedDate
  summary {
    text
  }
  subHeadline {
    text
  }
  body(customContents: $customContents, type: $bodyType) {
    text
  }
  keywords
  sections {
    value {
      name
      id
    }
  }
  topics {
    name
    entityId
    id
  }
  urlAlias
  authors {
    name
    id
  }
  images {
    style(filter: {style: "768x768"}) {
      url
    }
  }
  readingTime
}

fragment articleSourceHeaderArticle on Article {
  urlAlias
  ...entityLink
}

fragment authorBlockPrintArticleArticle on Article {
  ...defaultArticleDateContent
  ...authorNamesArticle
}

fragment authorNameAuthor on Author {
  ...entityLink
  name
  entityUuid
}

fragment authorNamesArticle on Article {
  authorLocations
  authors {
    entityId
    location
    ...authorNameAuthor
    id
  }
}

fragment blockquoteQuoteContent on Content {
  __isContent: __typename
  ...contentShareWidgetContent
}

fragment checkersCheckContentContainsStarlingImageContent on Content {
  __isContent: __typename
  topics {
    entityId
    id
  }
}

fragment contentHeadlineContent on Content {
  __isContent: __typename
  headline
  socialHeadline
  ...contentHeadlineTagContent
  ...helpersUseContentSponsorContent
}

fragment contentHeadlineTagContent on Content {
  __isContent: __typename
  ...hooksContentHeadlineTagContent
}

fragment contentNewsletterWidgetContent on Content {
  __isContent: __typename
  topics {
    relatedNewsletters {
      ...helpersMassageToNewsletterItemNewsletter
      id
    }
    id
  }
  sections {
    value {
      relatedNewsletters {
        ...helpersMassageToNewsletterItemNewsletter
        id
      }
      id
    }
  }
  ... on Article {
    relatedNewsletters {
      ...helpersMassageToNewsletterItemNewsletter
      id
    }
  }
}

fragment contentSchemaRenderContent on Content {
  __isContent: __typename
  ...blockquoteQuoteContent
  ...imageContent
  ...inlineWidgetContent
  ...photoGalleryWidgetContent
  ...scmpYoutubeContent
}

fragment contentShareWidgetContent on Content {
  __isContent: __typename
  entityId
  urlAlias
  shortUrl
  socialHeadline
  headline
}

fragment contentSponsorTagContent on Content {
  __isContent: __typename
  ...helpersUseContentSponsorContent
}

fragment contentSubHeadlineContent on Content {
  __isContent: __typename
  subHeadline {
    json
  }
  summary {
    json
  }
  ...contentSchemaRenderContent
}

fragment defaultArticleDateContent on Content {
  __isContent: __typename
  ...hooksArticleDateUtilsContent
}

fragment entityLink on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  __typename
  entityId
  entityUuid
  urlAlias
  urlRedirect {
    toUrl
    id
  }
  application {
    entityId
    id
  }
  ... on Section {
    fullSectionPath {
      entityId
      id
    }
    parentSection
  }
  ...helpersAppBarVariantBase
  ...helpersApplicationBase
  ...helpersCheckIsPlusArticle
  ...helpersStyleSectionContent
}

fragment helpersAppBarVariantBase on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  ...helpersCheckIsLiveArticle
  ...helpersCheckIsPlusPage
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostiesPage
  ...helpersCheckIsPostMagazineArticle
  ...helpersCheckIsStyleArticle
  ...helpersSectionContent
  ...helpersStyleSectionContent
}

fragment helpersApplicationBase on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostiesPage
  ...helpersCheckIsPlusPage
}

fragment helpersCheckIfNewsSectionInFirstIndexSection on Section {
  name
}

fragment helpersCheckIsAmpEnabledArticle on Article {
  entityId
  types {
    value {
      entityId
      id
    }
  }
  sections {
    value {
      entityId
      id
    }
  }
  disableOffPlatformContent
  sponsorType
  published
  ...helpersCheckIsPlusArticle
  ...helpersCheckIsPostiesArticle
}

fragment helpersCheckIsLiveArticle on Article {
  flattenTypeIds
  liveArticle {
    status
    id
  }
}

fragment helpersCheckIsMainTopicContent on Content {
  __isContent: __typename
  topics {
    entityId
    id
  }
}

fragment helpersCheckIsPlusArticle on Content {
  __isContent: __typename
  ... on Article {
    paywallTypes {
      entityUuid
      id
    }
  }
}

fragment helpersCheckIsPlusPage on Page {
  urlAlias
}

fragment helpersCheckIsPostMagazineArticle on Article {
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersCheckIsPostiesArticle on Article {
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersCheckIsPostiesPage on Page {
  urlAlias
}

fragment helpersCheckIsStyleArticle on Content {
  __isContent: __typename
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersGetArticleTypeArticle on Content {
  __isContent: __typename
  ... on Article {
    types {
      value {
        entityId
        id
      }
    }
  }
}

fragment helpersMassageToNewsletterItemNewsletter on Newsletter {
  entityId
  name
  alternativeName
  description {
    text
  }
  summary {
    text
  }
  homepageDescription {
    text
  }
}

fragment helpersSanitizeArticleTypeEntityIdsArticle on Article {
  types {
    value {
      entityId
      id
    }
  }
}

fragment helpersSanitizeAuthorTypesArticle on Article {
  authors {
    types
    id
  }
}

fragment helpersSanitizedAuthorEntityIdsArticle on Article {
  authors {
    entityId
    id
  }
}

fragment helpersSectionContent on Section {
  fullSectionPath {
    entityId
    id
  }
}

fragment helpersStyleSectionContent on Section {
  fullSectionPath {
    entityId
    id
  }
}

fragment helpersUseContentSponsorContent on Content {
  __isContent: __typename
  topics {
    entityId
    sponsor {
      ...sponsorTagSponsor
      name
      type
      id
    }
    id
  }
  ... on Article {
    sponsorType
  }
  ...helpersCheckIsMainTopicContent
}

fragment hooksArticleDateUtilsContent on Content {
  __isContent: __typename
  createdDate
  publishedDate
  updatedDate
}

fragment hooksArticleSeoArticle on Article {
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostMagazineArticle
  ...helpersCheckIsStyleArticle
  ...hooksContentHeadlineTagContent
  ...helpersCheckIsAmpEnabledArticle
  entityId
  headline
  socialHeadline
  types {
    value {
      entityId
      id
    }
  }
  authors {
    entityId
    id
  }
  images {
    generic_og: style(filter: {style: "og_image_scmp_generic"}) {
      url
    }
    styles(filter: {styles: ["og_image_posties_article", "og_postmag", "og_image_style", "og_image_scmp_analysis", "og_image_scmp_explainer", "og_image_scmp_editorial", "og_image_scmp_fact_check", "og_image_scmp_debate", "og_image_scmp_live", "og_image_scmp_obituary", "og_image_scmp_opinion", "og_image_scmp_review", "og_image_scmp_series", "og_image_scmp_generic"]}) {
      url
      style
    }
    type
  }
  urlAlias
}

fragment hooksContentHeadlineTagContent on Content {
  __isContent: __typename
  __typename
  ... on Article {
    types {
      value {
        name
        entityId
        description {
          text
        }
        id
      }
    }
    ...helpersCheckIsStyleArticle
  }
  flag
  sections {
    value {
      name
      id
    }
  }
  ...hooksContentHelperContent
}

fragment hooksContentHelperContent on Content {
  __isContent: __typename
  ...helpersSanitizeArticleTypeEntityIdsArticle
  ...helpersSanitizeAuthorTypesArticle
  ...helpersSanitizedAuthorEntityIdsArticle
  flag
}

fragment hooksPaywallPromiseContent on Content {
  __isContent: __typename
  entityId
  ...helpersCheckIsPostiesArticle
}

fragment hooksTrackPageViewArticle on Article {
  entityId
  publishedDate
  headline
  sections {
    value {
      name
      id
    }
  }
  urlAlias
  authors {
    name
    id
  }
  entityUuid
}

fragment imageContent on Content {
  __isContent: __typename
  headline
  ...checkersCheckContentContainsStarlingImageContent
}

fragment inlineWidgetContent on Content {
  __isContent: __typename
  ...contentNewsletterWidgetContent
}

fragment mainImagePrintArticleArticle on Article {
  images {
    title
    url
    isSlideshow
    size_652x446: style(filter: {style: "652x446"}) {
      url
    }
  }
}

fragment photoGalleryDialogContent on Content {
  __isContent: __typename
  __typename
  ...contentShareWidgetContent
}

fragment photoGalleryWidgetContent on Content {
  __isContent: __typename
  ...photoGalleryDialogContent
}

fragment scmpYoutubeContent on Content {
  __isContent: __typename
  entityId
  urlAlias
  publishedDate
}

fragment sponsorTagSponsor on Sponsor {
  name
  type
  images {
    url
  }
}


sections

types

disableOffPlatformContent

sponsorType

published

headline

socialHeadline

authors

images

publishedDate

updatedDate

summary

subHeadline

keywords

topics

readingTime

authorLocations

entityUuid

Holly Chik

Scientists in Thailand have begun generating hydrogen plasma with the help of a device known as a tokamak, recently donated by China, in a bid to position the region as a hub for research on clean fusion energy.
The team said they were confident the device – known as Thailand Tokamak-1 (TT-1) – will reach its full capacity this month, opening the door for research, and the possibility of further raising the temperature inside the machine.
A tokamak – a doughnut-shaped device built to harness the energy of fusion – produces an extremely powerful magnetic field to contain and control hydrogen gas that is 10 times hotter than the core of the sun.
The thermonuclear fusion reaction – the same process that has kept the sun burning for the past 5 billion years – is seen as the ultimate solution to humanity’s future energy needs. Unlike today’s uranium-fuelled nuclear power plants, a fusion reactor would produce no radioactive waste.
The refurbished device was developed and donated by the Chinese Academy of Sciences’ Institute of Plasma Physics (ASIPP) in Hefei, Anhui province, where it had operated for 18 years up to 2002.
US bank collapses may stall Asia’s clean energy transition, from China to India
TT-1 is expected to help train scientists and engineers from Thailand and Asean member states. Last month, the Thai researchers, along with Chinese peers who offer on-site support, began testing the device after it was installed.
The first successful test happened on April 21, said Nopporn Poolyarat, head of Thailand Institute of Nuclear Technology’s nuclear fusion and plasma division, who spoke to the Post from where TT-1 is located, about 90km (56 miles) northeast of Bangkok.
“On that morning we still had some problems to fix. Later in the afternoon, we tried again and suddenly we got the first breakdown. Everyone was happy. Even though it was a small breakdown, at least we saw plasma,” he said.


Fusion energy is produced by nuclear fusion reactions, which occur at extremely high temperatures. During the reaction, two atomic nuclei – isotopes of hydrogen deuterium and tritium in this case – fuse together to form a heavier nucleus and release huge amounts of energy.
The fusion reactions take place in a state of matter called plasma – a super hot ionised gas. The term “breakdown” refers to a transition process from insulating gas to conducting plasma.
The electric current produced in the first plasma was measured at 2,000 amperes, rather small compared to what the team achieved during their training in China. Nopporn was part of a nine-member team that spent three months in Hefei last year to learn how to operate a tokamak.
“In the beginning we wanted to make sure the connection and the system were OK. Putting a lot of energy into the plasma at the beginning might not be a good idea because it can damage the machine. We then increased it step by step,” he said.
Since then, the team has heated the plasma to a range of 60,000 to 70,000 amperes, which lasted 0.05 second. The key focus for now is to raise the plasma temperature to a maximum capacity of 100,000 amperes for 0.1 second by mid-May.
“More plasma particles means more fusion creation, and more energy could be generated,” Nopporn said.
Chinese scientists have been on site offering technical support since before the tokamak arrived in January, according to Somsak Dangtip, manager of the Thai institute’s advanced engineering and nuclear technology centre.
“In December, a crew from ASIPP visited to inspect the site. Another engineer group later came to unpack the cargo and started installing the machine. It’s the fourth group staying with us at the moment,” Somsak said.
After the final group of Chinese engineers leaves Thailand later this month, they will stay in contact to offer operational and maintenance support.
The team from the Thai institute has also been working closely with staff from the country’s largest power producer, the Electricity Generating Authority of Thailand (EGAT), who have taken part in training, installation and operation of the machine, Somsak said.
“EGAT sees this group of young staff as the future major force if it wants to continue with fusion energy as the new energy source to generate electricity for Thailand,” he said.
Nopporn said the local team also has plans to upgrade the machine, including using artificial intelligence to help keep operations smooth.
“Right now we have a basic set of components to generate plasma. To raise the temperature of the plasma, we need to add more heating components. We also need more diagnostic tools to measure the properties of plasma.”


He also said the team would study ways to increase the temperature of plasma using a physical phenomenon known as a “transport barrier”, an area of study that is attracting growing attention from scientists around the world.
“Inside the tokamak it is really hot, and heat is lost to the outside. But if we can trigger the so-called transport barrier, the heat could be more or less confined and not transferred outside easily so that we can keep the temperature inside very high,” he said, adding that the same machine reached 2 million degrees Celsius (3.6 million Fahrenheit) while it was in China.
In preparation for the departure of the Chinese engineers, the Thai researchers have started to operate the machine on their own.
Hydrogen could hold the key to China’s zero-carbon ambitions
“Since we are 30 years behind China, we need to learn how to control the plasma, how to raise its temperature and how to make the fusion reaction occur in Thailand, Nopporn said.
“Step by step we build confidence that we will have enough [trained] manpower. When the [fusion power] technology comes, we can use it wisely.”


A Chinese-made fusion reactor is creating breakdowns – Thai scientists are delighted

A team of Chinese and Thai scientists say they are confident the Thailand Tokamak-1 will reach its full capacity this month, opening the door for more  research on clean fusion energy. Photo: handout

News

China

Science

Using a tokamak reactor donated by China, researchers in Thailand are generating hydrogen plasma to learn more about nuclear fusion
The country has joined the pursuit of clean fusion energy, considered the ultimate solution to humanity’s future power needs


Using a tokamak reactor donated by China, researchers in Thailand are generating hydrogen plasma to learn more about nuclear fusion.


A Chinese-made fusion reactor is creating breakdowns – Thai scientists are delighted

Using a tokamak reactor donated by China, researchers in Thailand are generating hydrogen plasma to learn more about nuclear fusion The country has joined the pursuit of clean fusion energy, considered the ultimate solution to humanity’s future power needs

Using a tokamak reactor donated by China, researchers in Thailand are generating hydrogen plasma to learn more about nuclear fusion

The country has joined the pursuit of clean fusion energy, considered the ultimate solution to humanity’s future power needs