Premium
The complex relationship between the light‐entrainable and methamphetamine‐sensitive circadian oscillators: evidence from behavioral studies of P eriod ‐mutant mice
European Journal Of NeurosciencePeer ReviewedPendergast Julie S. +22013Journals
The methamphetamine‐sensitive circadian oscillator ( MASCO ) is an enigmatic circadian clock whose output is observed during continuous consumption of low‐dose methamphetamine. The MASCO rhythm persists when the light‐entrainable pacemaker in the suprachiasmatic nucleus ( SCN ) is lesioned, but the anatomical location of MASCO is unknown. We recently found that the period of the MASCO rhythm is unusually short (21 h) in mice with disruption of all three paralogs of the canonical clock gene, P eriod . In this study, we investigated the contribution of each P eriod paralog to timekeeping in MASCO . We measured wheel‐running activity rhythms in intact and SCN ‐lesioned P er1 ‐, 2 ‐ and 3 ‐mutant mice administered methamphetamine, and found that none of the mice displayed a short (21‐h) period, demonstrating that no single P eriod gene is responsible for the short‐period MASCO rhythm of P er1 −/− / P er2 −/− / P er3 −/− mice. We also found that the periods of activity rhythms in constant darkness were lengthened by methamphetamine treatment in intact wild‐type, P er1 −/− and P er3 −/− mice but not P er2 −/− mice, and P er2 −/− mice had two distinct activity rhythms upon release to constant light. These data suggest that the SCN and MASCO are not coupled in P er2 −/− mice. The MASCO rhythm in P er1 −/− / P er2 −/− mice in constant darkness alternated between a short (22‐h) and a long (27‐h) period. This pattern could result from two coupled oscillators that are not synchronised to each other, or from a single oscillator displaying birhythmicity. Finally, we propose a working model of the in vivo relationship between MASCO and the SCN that poses testable hypotheses for future studies.
This content is not available in your region!
Continue researching from Zendy home
Having issues? Contact support