Search results
From Polyphasic Sleep Wiki
Page title matches
- Cores are longer blocks of sleep that contain one or more full sleep cycles. They204 bytes (32 words) - 11:23, 14 January 2021
- 213 bytes (2 words) - 11:23, 14 January 2021
- 8 bytes (0 words) - 11:23, 14 January 2021
Page text matches
- ...l short cores, such as [[Special:MyLanguage/QC0|QC0]] (4 cores) and PC0 (5 cores), can also be used to create non-reducing schedules.176 bytes (25 words) - 20:45, 25 January 2021
- ...lyphasic schedules are broadly categorised into [[Special:MyLanguage/cores|cores]] and [[Special:MyLanguage/naps|naps]].132 bytes (17 words) - 09:30, 30 December 2020
- ...ate for the lost REM time from having a shorter [[Special:MyLanguage/cores|cores]].228 bytes (37 words) - 11:24, 14 January 2021
- [[File:DC1-mod.png|thumb|Slightly shortened/extended cores]] ...REM need. The higher total sleep also increases the potential to flex the cores after adaptation. This variant is considered viable, though the second core309 bytes (51 words) - 21:07, 7 January 2021
- ...:Polyphasic Sleep Schedules|schedule]] with two [[Special:MyLanguage/cores|cores]] at night, usually with a total sleep time close to one's personal [[Speci288 bytes (37 words) - 09:33, 30 December 2020
- ...de the necessary amount of SWS to sustain life. As such, schedules without cores (i.e. [[Special:MyLanguage/Nap only|nap only schedules]]) have extremely lo584 bytes (99 words) - 09:30, 30 December 2020
- A '''tri core''' schedule is a sleep schedule with three [[Cores|core sleeps]]. ...ist of three cores, splitting further [[dual core]] schedules. Each of the cores has only one sleep cycle by default, with the length around 1.5h.2 KB (269 words) - 04:23, 6 January 2021
- [[Cores|Ядра]]18 bytes (1 word) - 14:16, 23 November 2020
- [[File:DC1-30m.png|thumb|30min naps and shortened cores]] ...ntly less total sleep than standard DC1. They extend the night and morning cores, while shortening the daytime core of Triphasic to a 30m nap for ease of sc437 bytes (69 words) - 21:07, 7 January 2021
- == Esquema de cores Napchart ==31 bytes (4 words) - 02:12, 23 January 2021
- ...d 1 nap. Sometimes more cores/naps can be used to reduce total sleep. Both cores and naps are flexible.598 bytes (75 words) - 05:54, 27 December 2020
- ...d 1 nap. Sometimes more cores/naps can be used to reduce total sleep. Both cores and naps are flexible.562 bytes (72 words) - 05:54, 27 December 2020
- ...that has been adapted to so far is 9 hours between the daytime and evening cores. Other gaps are expected to be smaller, as sleep pressure is higher at nigh397 bytes (68 words) - 12:02, 5 January 2021
- ===Shortened cores and 30-minute naps===40 bytes (5 words) - 21:07, 7 January 2021
- ...d 1 nap. Sometimes more cores/naps can be used to reduce total sleep. Both cores and naps are flexible.632 bytes (79 words) - 08:41, 23 December 2020
- 多相時程上的睡眠主要分為[[Special:MyLanguage/cores|主段睡眠]]和[[Special:MyLanguage/naps|小睡]]。117 bytes (6 words) - 04:59, 1 July 2021
- 多相时程上的睡眠主要分为[[Special:MyLanguage/cores|主段睡眠]]和[[Special:MyLanguage/naps|小睡]]。117 bytes (6 words) - 10:36, 5 July 2021
- ...phasic|бифазный график]], который состоит из длинного [[Special:MyLanguage/Cores|ядра]] ночью и более короткого днем.221 bytes (7 words) - 14:00, 20 December 2020
- 多相スケジュールでの睡眠は、[[Special:MyLanguage/cores|コア]]と[[Special:MyLanguage/naps|仮眠]]に大きく分けられてい153 bytes (6 words) - 01:11, 18 March 2021
- Cores are longer blocks of sleep that contain one or more full sleep cycles. They138 bytes (23 words) - 11:24, 14 January 2021
- Cores are longer blocks of sleep that contain one or more full sleep cycles. They138 bytes (23 words) - 11:24, 14 January 2021
- Сон на поліфазних графіках в цілому підрозділяється на [[Special:MyLanguage/cores|ядра]] та [[Special:MyLanguage/naps|непи]].182 bytes (6 words) - 02:46, 31 December 2020
- Сон на полифазных графиках в целом подразделяется на [[Special:MyLanguage/cores|ядра]] и [[Special:MyLanguage/naps|нэпы]].176 bytes (6 words) - 08:55, 9 December 2020
- ...inheiten in polyphasische Schlafmuster werden grob in [[Special:MyLanguage/cores|Kerne]] und [[Special:MyLanguage/naps|Nickerchen]] eingeteilt.150 bytes (17 words) - 14:59, 23 January 2021
- ...nogramas polifáscicos são geralmente classificados em [[Special:MyLanguage/cores|núcleos]] e [[Special:MyLanguage/naps|sonecas]].144 bytes (20 words) - 03:44, 24 January 2021
- ...to the the nightly core gap reducing the amount of time awake between the cores during the day.844 bytes (135 words) - 09:33, 30 December 2020
- ...з линейки Everyman. По умолчанию он содержит 2 нэпа и [[Special:MyLanguage/Cores|ядро]] длительностью 4.5 часа (3 полных цикл281 bytes (10 words) - 02:27, 30 December 2020
- ...й логически следует за [[Segmented|Сегментированным сном]], сокращая его [[Cores|ядро]] (обычно второе) и добавляя [[Naps|нэп]],398 bytes (12 words) - 14:39, 23 November 2020
- Cores are longer blocks of sleep that contain one or more full sleep cycles. They204 bytes (32 words) - 11:23, 14 January 2021
- ...ня, часто чтобы компенсировать потерянное время REM сна из-за сокращения [[cores|ядер]].376 bytes (5 words) - 11:23, 14 January 2021
- The longer night gap between the cores may also not be suitable for everyone, because staying awake for many hours175 bytes (29 words) - 21:07, 7 January 2021
- ...e/Tri core|семейства графиков]], который состоит из 3 [[Special:MyLanguage/Cores|ядер]] и не содержит нэпов.285 bytes (9 words) - 04:58, 6 January 2021
- |data4 = 2 cores, aligned to SWS and REM peaks.359 bytes (41 words) - 05:54, 27 December 2020
- |data4 = 2 cores, aligned to SWS and REM peaks.323 bytes (38 words) - 05:54, 27 December 2020
- |data4 = 2 cores, aligned to SWS and REM peaks.393 bytes (45 words) - 08:46, 23 December 2020
- ...ule in the Everyman line. It consists of 2 naps and a [[Special:MyLanguage/Cores|core]] sleep of 4.5h (3 full cycles) by default.<ref name="pd" />190 bytes (32 words) - 02:27, 30 December 2020
- ...cronogramas Everyman. Ele consiste em 2 sonecas e um [[Special:MyLanguage/Cores|núcleo]] de sono de 4.5h (3 ciclos completos) por padrão.<ref name="pd" /215 bytes (34 words) - 00:13, 9 February 2023
- |data4 = 1 cores, 3 30-minute naps, in dymaxion configuration.415 bytes (45 words) - 05:54, 27 December 2020
- |data4 = 1 cores, 3 30-minute naps, in dymaxion configuration.379 bytes (42 words) - 05:54, 27 December 2020
- |data4 = 2 cores, 2 naps, in dymaxion configuration.394 bytes (44 words) - 05:52, 27 December 2020
- |data4 = 2 cores, 2 naps, in dymaxion configuration.430 bytes (47 words) - 05:52, 27 December 2020
- ...hasic Sleep Schedules|графік]], що складається з двох [[Special:MyLanguage/cores|ядер]] вночі, зазвичай із загальним часом453 bytes (16 words) - 03:19, 31 December 2020
- |data4 = 2 cores and 4 naps in an Uberman configuration.411 bytes (47 words) - 05:54, 27 December 2020
- |data4 = 2 cores and 4 naps in an Uberman configuration.375 bytes (44 words) - 05:54, 27 December 2020
- ...Tri core]] original e mais popular, que consiste em 3 [[Special:MyLanguage/Cores|núcleos]] e nenhuma [[Special:MyLanguage/naps|soneca]].194 bytes (28 words) - 00:12, 9 February 2023
- |data4 = 2 long cores at night aligned to SWS and REM peaks respectively.443 bytes (53 words) - 05:54, 27 December 2020
- |data4 = 2 long cores at night aligned to SWS and REM peaks respectively.407 bytes (50 words) - 05:54, 27 December 2020
- |data4 = 1 cores, 3 30-minute naps, in dymaxion configuration.449 bytes (49 words) - 08:54, 23 December 2020
- |data4 = 2 cores and 4 naps in an Uberman configuration.445 bytes (51 words) - 08:29, 23 December 2020
- The benefits of this variant is the flexibility of the naps and cores. Out of all polyphasic schedules with 4-4.5h total sleep ("Hard" and "Very197 bytes (34 words) - 07:24, 31 December 2020
- ...ции потерянного времени быстрого сна из-за сокращения [[Special:MyLanguage/cores|ядер]].466 bytes (6 words) - 13:06, 24 June 2021
- ...ции потерянного времени быстрого сна из-за сокращения [[Special:MyLanguage/cores|ядер]].453 bytes (5 words) - 13:05, 24 June 2021
- |data4 = 2 long cores at night aligned to SWS and REM peaks respectively.477 bytes (57 words) - 08:45, 23 December 2020
- |data4 = 2 cores, 2 naps, in dymaxion configuration.510 bytes (56 words) - 09:59, 14 January 2021
- ...age/Tri core|Tri core]] schedule, which consists of 3 [[Special:MyLanguage/Cores|core]] sleeps and no [[Special:MyLanguage/naps|naps]].195 bytes (28 words) - 12:02, 5 January 2021
- |data4 = 2 cores, multiple short naps393 bytes (52 words) - 20:12, 9 January 2021
- Dividing the monophasic core into several cores can be beneficial for intense exercising schedule, since the refreshment fr316 bytes (52 words) - 20:45, 25 January 2021
- ...e [[Tri core|Tri-core]] line<ref name="lich" />, which consists of three [[cores]] and two [[naps]]. ...aps inserted in the day to maintain the alertness. The scheduling of the 3 cores resembles that of the 3 naps on [[Dymaxion]].4 KB (606 words) - 05:31, 15 January 2021
- The idea behind this variant is similar to Siesta, but with both cores at night, and with the short core providing much of the SWS. Sleepers with327 bytes (55 words) - 09:33, 30 December 2020
- |data4 = 2 cores, multiple short naps485 bytes (60 words) - 20:15, 9 January 2021
- ...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
- ...ntial, and may allow for a more complete repartitioning. However, 2.5-hour cores increase the likelihood for SWS wakes, which increases the chance for overs559 bytes (91 words) - 21:07, 7 January 2021
- === Additional cores === This modification makes Naptation less extreme. [[Cores|Core(-s)]] partially or fully account for SWS, which delays SWS rebound and3 KB (513 words) - 19:59, 9 January 2021
- ...leeps. This boosts alertness and keeps sleep pressures low. The four short cores may also promote sleep compression. ...ith SWS, whereas the morning one contains much more REM. The remaining two cores, one at night and one in the day, contain mixed sleep stages and likely mor5 KB (738 words) - 20:00, 9 January 2021
- ...оротким дневным [[Special:MyLanguage/Naps|нэпом]] или [[Special:MyLanguage/Cores|ядром]]. Однако считается, что подобные гр910 bytes (17 words) - 06:56, 3 February 2021
- Dual Core 2, or DC2, is the second [[Dual core|Dual core schedule]], with two cores and two naps.<ref name="polysoc" /> The total sleep of DC2 is around 5 to 5 ...adaptation. Compared to [[E2]], which has a similar total sleep, the split cores may allow for more efficient sleep. Four sleeps per day keeps sleep pressur7 KB (1,191 words) - 09:51, 16 January 2021
- ...g sleepers, whereas the latter aims not to reduce any sleep (e.g, 4.5-4.5h cores for a 9-hour sleeper). The non-reducing variant is believed to resemble the566 bytes (84 words) - 20:45, 25 January 2021
- This schedule also belongs to the [[dual core]] category by the amount of cores, albeit the mechanism is quite different from segmented/bifurcated sleep. B This schedule belongs to the [[dual core]] category both by the amount of cores and by the mechanism of segmentation and is a nice starting point for the g3 KB (504 words) - 05:08, 6 January 2021
- ...age/Tri core|Tri core]] schedule, which consists of 3 [[Special:MyLanguage/Cores|core]] sleeps and no [[Special:MyLanguage/naps|naps]]. ...that has been adapted to so far is 9 hours between the daytime and evening cores. Other gaps are expected to be smaller, as sleep pressure is higher at nigh5 KB (788 words) - 05:14, 6 January 2021
- |No cores and any number of naps646 bytes (105 words) - 09:30, 30 December 2020
- ...use non-reducing Segmented already provides all the necessary sleep in the cores, and does not require taking any daytime naps.671 bytes (103 words) - 20:45, 25 January 2021
- 888 bytes (28 words) - 03:01, 25 December 2020
- ...age/Tri core|Tri core]] schedule, which consists of 3 [[Special:MyLanguage/Cores|core]] sleeps and no [[Special:MyLanguage/naps|naps]]. ...that has been adapted to so far is 9 hours between the daytime and evening cores. Other gaps are expected to be smaller, as sleep pressure is higher at nigh5 KB (842 words) - 05:13, 6 January 2021
- ...edules resemble Dymaxion. Starting from Bimaxion, one [[Special:MyLanguage/Cores|core]] is shortened to 30 m after adapting to the previous schedule until e663 bytes (101 words) - 07:27, 31 December 2020
- ...ism of Ducamayl is believed to resemble that of Sevamayl, with two shorter cores in place of the long Everyman core. ...pers, the schedule would include at least ~4-5 hours of sleep from the two cores, with about 1-4 naps of 10-20 minutes in length. Nap spacing should take in10 KB (1,584 words) - 20:12, 9 January 2021
- ...day whenever is tired enough. The concept resembles [[Spamayl]], but short cores are used in place of [[naps]]. {{TNT|Camayl}} ...the new reduced sleep total. It is then possible to start [[flexing]] the cores, which contain repartitioned [[wikipedia:Slow-wave_sleep|SWS]] and [[wikipe6 KB (1,027 words) - 07:46, 12 January 2021
- Because of Triphasic's daytime and evening cores at often inconvenient hours, Triphasic is not very popular. The need for a757 bytes (122 words) - 12:02, 5 January 2021
- ...re can be moved to ~16-17. The shorter gap between the evening and morning cores resembles Segmented core gap and can be utilized for various activities. Th890 bytes (144 words) - 12:02, 5 January 2021
- == Esquema de cores Napchart ==3 KB (530 words) - 03:43, 24 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 o ...nd as with all other Dual core schedules, it is much less tolerant to late cores.10 KB (1,632 words) - 08:27, 13 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 o ...nd as with all other Dual core schedules, it is much less tolerant to late cores.10 KB (1,736 words) - 08:26, 13 January 2021