home.social

#empiar — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #empiar, aggregated by home.social.

  1. In 2021, I was involved in a study of the #chromatin remodeler ALC1, a protein involved in the early events of the DNA damage response. This led to a paper summarized in a previous thread: fediscience.org/@Guillawme/111

    We had deposited the raw #cryoEM data to #EMPIAR (dataset EMPIAR-10739), which is the primary reason this new preprint could come to exist at all.

    This figure shows the structural knowledge available on ALC1 up to the point of the new structure we report in the preprint. An AlphaFold2 prediction, a structure of the auto-inhibited conformation, and a few structures of ALC1-nucleosome complexes. Notably, none of the structures of nucleosome complexes resolved the macro domain. This is a significant gap, because the macro domain is key in regulating ALC1: it is responsible for auto-inhibition and recruitment to PARylated nucleosomes, and these two things are exclusive, which is why recruitment also causes release of the auto-inhibition. So at this point we know what the protein looks like when auto-inhibited and when active, but how it transitions from the former to the latter is unclear.

    2/5

  2. In 2021, I was involved in a study of the #chromatin remodeler ALC1, a protein involved in the early events of the DNA damage response. This led to a paper summarized in a previous thread: fediscience.org/@Guillawme/111

    We had deposited the raw #cryoEM data to #EMPIAR (dataset EMPIAR-10739), which is the primary reason this new preprint could come to exist at all.

    This figure shows the structural knowledge available on ALC1 up to the point of the new structure we report in the preprint. An AlphaFold2 prediction, a structure of the auto-inhibited conformation, and a few structures of ALC1-nucleosome complexes. Notably, none of the structures of nucleosome complexes resolved the macro domain. This is a significant gap, because the macro domain is key in regulating ALC1: it is responsible for auto-inhibition and recruitment to PARylated nucleosomes, and these two things are exclusive, which is why recruitment also causes release of the auto-inhibition. So at this point we know what the protein looks like when auto-inhibited and when active, but how it transitions from the former to the latter is unclear.

    2/5

  3. In 2021, I was involved in a study of the #chromatin remodeler ALC1, a protein involved in the early events of the DNA damage response. This led to a paper summarized in a previous thread: fediscience.org/@Guillawme/111

    We had deposited the raw #cryoEM data to #EMPIAR (dataset EMPIAR-10739), which is the primary reason this new preprint could come to exist at all.

    This figure shows the structural knowledge available on ALC1 up to the point of the new structure we report in the preprint. An AlphaFold2 prediction, a structure of the auto-inhibited conformation, and a few structures of ALC1-nucleosome complexes. Notably, none of the structures of nucleosome complexes resolved the macro domain. This is a significant gap, because the macro domain is key in regulating ALC1: it is responsible for auto-inhibition and recruitment to PARylated nucleosomes, and these two things are exclusive, which is why recruitment also causes release of the auto-inhibition. So at this point we know what the protein looks like when auto-inhibited and when active, but how it transitions from the former to the latter is unclear.

    2/5

  4. In 2021, I was involved in a study of the #chromatin remodeler ALC1, a protein involved in the early events of the DNA damage response. This led to a paper summarized in a previous thread: fediscience.org/@Guillawme/111

    We had deposited the raw #cryoEM data to #EMPIAR (dataset EMPIAR-10739), which is the primary reason this new preprint could come to exist at all.

    This figure shows the structural knowledge available on ALC1 up to the point of the new structure we report in the preprint. An AlphaFold2 prediction, a structure of the auto-inhibited conformation, and a few structures of ALC1-nucleosome complexes. Notably, none of the structures of nucleosome complexes resolved the macro domain. This is a significant gap, because the macro domain is key in regulating ALC1: it is responsible for auto-inhibition and recruitment to PARylated nucleosomes, and these two things are exclusive, which is why recruitment also causes release of the auto-inhibition. So at this point we know what the protein looks like when auto-inhibited and when active, but how it transitions from the former to the latter is unclear.

    2/5

  5. In 2021, I was involved in a study of the #chromatin remodeler ALC1, a protein involved in the early events of the DNA damage response. This led to a paper summarized in a previous thread: fediscience.org/@Guillawme/111

    We had deposited the raw #cryoEM data to #EMPIAR (dataset EMPIAR-10739), which is the primary reason this new preprint could come to exist at all.

    This figure shows the structural knowledge available on ALC1 up to the point of the new structure we report in the preprint. An AlphaFold2 prediction, a structure of the auto-inhibited conformation, and a few structures of ALC1-nucleosome complexes. Notably, none of the structures of nucleosome complexes resolved the macro domain. This is a significant gap, because the macro domain is key in regulating ALC1: it is responsible for auto-inhibition and recruitment to PARylated nucleosomes, and these two things are exclusive, which is why recruitment also causes release of the auto-inhibition. So at this point we know what the protein looks like when auto-inhibited and when active, but how it transitions from the former to the latter is unclear.

    2/5

  6. When depositing #cryoEM data to #EMPIAR, I can never remember how to determine the "voxel type" requested in the metadata entry form.

    Over the years, I have asked about it on CCPEM, bookmarked the permalink to the answer I received back then (probably in multiple browser profiles) and written similar notes at different places in my system.

    Here is one more note about it, this time public: gaullier.org/en/blog/2025/06/0

  7. When depositing #cryoEM data to #EMPIAR, I can never remember how to determine the "voxel type" requested in the metadata entry form.

    Over the years, I have asked about it on CCPEM, bookmarked the permalink to the answer I received back then (probably in multiple browser profiles) and written similar notes at different places in my system.

    Here is one more note about it, this time public: gaullier.org/en/blog/2025/06/0

  8. When depositing #cryoEM data to #EMPIAR, I can never remember how to determine the "voxel type" requested in the metadata entry form.

    Over the years, I have asked about it on CCPEM, bookmarked the permalink to the answer I received back then (probably in multiple browser profiles) and written similar notes at different places in my system.

    Here is one more note about it, this time public: gaullier.org/en/blog/2025/06/0

  9. When depositing #cryoEM data to #EMPIAR, I can never remember how to determine the "voxel type" requested in the metadata entry form.

    Over the years, I have asked about it on CCPEM, bookmarked the permalink to the answer I received back then (probably in multiple browser profiles) and written similar notes at different places in my system.

    Here is one more note about it, this time public: gaullier.org/en/blog/2025/06/0

  10. When depositing #cryoEM data to #EMPIAR, I can never remember how to determine the "voxel type" requested in the metadata entry form.

    Over the years, I have asked about it on CCPEM, bookmarked the permalink to the answer I received back then (probably in multiple browser profiles) and written similar notes at different places in my system.

    Here is one more note about it, this time public: gaullier.org/en/blog/2025/06/0

  11. @jeremyforest @jonny

    Hosting scientific data in the corporate cloud is a bad idea, given current costs and the volatility of the digital storage industry.

    Projects like #EMPIAR ebi.ac.uk/empiar/ seems more capable and likely to survive into the future.

  12. @jeremyforest @jonny

    Hosting scientific data in the corporate cloud is a bad idea, given current costs and the volatility of the digital storage industry.

    Projects like #EMPIAR ebi.ac.uk/empiar/ seems more capable and likely to survive into the future.

  13. @jeremyforest @jonny

    Hosting scientific data in the corporate cloud is a bad idea, given current costs and the volatility of the digital storage industry.

    Projects like #EMPIAR ebi.ac.uk/empiar/ seems more capable and likely to survive into the future.

  14. @jeremyforest @jonny

    Hosting scientific data in the corporate cloud is a bad idea, given current costs and the volatility of the digital storage industry.

    Projects like #EMPIAR ebi.ac.uk/empiar/ seems more capable and likely to survive into the future.

  15. @jeremyforest @jonny

    Hosting scientific data in the corporate cloud is a bad idea, given current costs and the volatility of the digital storage industry.

    Projects like #EMPIAR ebi.ac.uk/empiar/ seems more capable and likely to survive into the future.

  16. ! 😍
    ---
    RT @ribo_rob
    Happy to share @cryocloud_io's first blog article & benchmark! Huge thanks to @SjorsScheres for making , & @RadoDanev for uploading the data to - this would not have been possible otherwise!
    twitter.com/cryocloud_io/statu
    twitter.com/ribo_rob/status/16