Search results
From Polyphasic Sleep Wiki
- ...aning that the sleep stages becomes less distinctly allocated into the two cores. The longer first core may also resemble Siesta, with the second sleep look392 bytes (67 words) - 09:33, 30 December 2020
- ...an [[Special:MyLanguage/E3|E3]], due to the need to split SWS over several cores as well as its longer gaps.284 bytes (50 words) - 12:02, 5 January 2021
- Note that pronaps on regular E3 is not recommended, as the 3 or 3.5h cores may not cover all SWS needs when adaptation first begins. Extending the fir302 bytes (55 words) - 07:24, 31 December 2020
- ...for non-natural Segmented sleepers. The reason for this is to prevent the cores from becoming [[Special:MyLanguage/interrupted sleep|interrupted sleep]] an361 bytes (55 words) - 20:06, 7 January 2021
- ...to appear then. After adaptation, naps can be relatively flexible, whereas cores are much harder to move.373 bytes (62 words) - 09:30, 30 December 2020
- |data4 = 2 cores, multiple short naps530 bytes (66 words) - 19:59, 9 January 2021
- '''Tri Core 1''', or '''TC1''', is a schedule with 3 single cycle [[Core|cores]] and 1 [[nap]], as a part of the [[Tri core]] schedule family.<ref name="p ...he middle core is likely to contain mixed stages. The wake gap between the cores should be at least 2h to facilitate falling asleep in each core and avoid i3 KB (488 words) - 04:00, 15 January 2021
- Using slightly shortened cores would be more difficult, as it has less total sleep time. Repartitioning of435 bytes (72 words) - 21:07, 7 January 2021
- ...WS may be required, which can cause difficult SWS wakes from either of the cores. High SWS requirements (at least ~150m) will likely require the extension o310 bytes (54 words) - 21:07, 7 January 2021
- ...схеме именования полифазных расписаний, E3 содержит 1 [[Special:MyLanguage/Cores|ядро]] и 3 [[Special:MyLanguage/naps|нэпа]].<ref name="pd" />556 bytes (27 words) - 02:08, 23 December 2020
- This variant, which is rarely attempted, has cores of slightly different lengths. These variants allows for slightly more time515 bytes (80 words) - 09:33, 30 December 2020
- ...nd as with all other Dual core schedules, it is much less tolerant to late cores.353 bytes (65 words) - 21:07, 7 January 2021
- 675 bytes (29 words) - 13:13, 30 December 2020
- ...uage/Everyman|Everyman]], который состоит из длинного [[Special:MyLanguage/Cores|ядра]], обычно длящегося 6 часов, и коротко692 bytes (29 words) - 13:13, 30 December 2020
- ...y/ post]. After some revisions, it became its current form, with 2 short [[cores]] and 2 30-minute [[naps]]. Later, it was renamed to "Bimaxion" to match [[ ...ule, with SWS and REM mostly being repartitioned into the first and second cores, respectively. However, unlike a shortened [[DC2]], Bimaxion's distribution4 KB (553 words) - 09:57, 14 January 2021
- ...the total sleep of the whole schedule is 4h, which, along with the divided cores, makes it one of the most difficult schedules that an average sleeper may b ...e SWS required during the first short core. Given the low total sleep, the cores should be scheduled close to the SWS peak to ensure the preservation of SWS4 KB (736 words) - 03:07, 10 January 2021
- ...g the naming scheme of polyphasic schedules, E3 has 1 [[Special:MyLanguage/Cores|core]] sleep and 3 [[Special:MyLanguage/naps|naps]].<ref name="pd" />413 bytes (61 words) - 07:24, 31 December 2020
- ...guage/Everyman|Everyman]] line, which contains a long [[Special:MyLanguage/Cores|core]], usually with a length of 6 hours, and a short [[Special:MyLanguage/513 bytes (74 words) - 03:49, 25 January 2021
- ...rk (at ~16-17). These are also known to be much more flexible, both in the cores and in the nap. After adapting, one can also proceed to [[Special:MyLanguag481 bytes (88 words) - 19:58, 9 January 2021
- ...pplied with a short [[Special:MyLanguage/Naps|nap]] / [[Special:MyLanguage/Cores|core]] midday. However, all of the schedules practiced are believed to not556 bytes (81 words) - 20:45, 25 January 2021