PSC camp will be held at Green Bank from July 28 to August 3 and applications are open!

Knowledge Base

Pulsar FAQ



Pulsar Properties



Why do we add pulses together?

Once the PRESTO software guesses a period, it “folds” the data at that period. If the hypothetical period is 1 second, PRESTO would split the data into 1-second chunks (150 of them, for the 2.5 minutes of data). These chunks are then lined up and added together, so that the strength of the signal at 0.1 seconds is added to the strength of the signal at 1.1 seconds, and that is added to the strength at 2.1 seconds, etc.

An individual pulse from a pulsar can be weak and may not rise far enough above the noise. But if the data are folded at a pulsar’s period, the noise starts to cancel itself out (forming a flat baseline), while the pulses add constructively and pop out more noticeably.

These added pulses are called the “average pulse profile.” While individual pulses may vary in shape, their average shape is very stable.

Why is the pulse profile plotted twice?


If the pulse profile were only plotted one time, plots such as the one shown here would be a problem. The pulsar would only show up at the edge of the average pulse profile subplot, and it might not be recognized as a pulsar. So PRESTO plots the same exact pulse profile two times, so that no matter where the pulse came in time-wise, it will be seen in full.

The other subplots also have information plotted twice. The subplot below the pulse profile is called the time domain plot.

Why are there more than two pulses in the pulse profile?


Sometimes, the software guesses a period that is close, but not quite right. If it guesses a period that is twice the pulsar’s actual period, the average signal will still pop above the noise, but there will be two pulses in the pulse profile, and then those two pulses will be plotted twice (so that four pulses would appear in the average pulse profile subplot). If the guessed period is three times the actual period, there will be six pulses in the profile.

Why do the RA and Dec on my plot not match the RA and Dec in the ATNF catalog?

The data that you analyze using the database was taken at 350 MHz. This “beam” is really big. What this means is that when the telescope points at the sky, it can see one spot and it is about the size of the moon. Another way to think of this is using a digital camera as an example. Most digital cameras now are many megapixels; a 4 mexapixel camera has 4 million little pixels on the CCD chip inside.

When you take a picture, each pixel captures a little bit of different light and when you put all the pixels together, you get an image. And you can’t see anything smaller than a pixel; the resolution of your image is dependent on the size and number of pixels. The GBT is somewhat similar, but for pulsar observing, it only has one pixel. The size of the pixel is determined by the radio frequency: the lower the frequency, the larger the pixel. So, at 350 MHz, the pixel is really big (about the size of the full moon).

The RA and Dec can vary a bit too, so don’t be surprised if that differs from what is on your plot. It is a common misconception that it is because the pulsar moved. The reason it varies is this: The way the telescope works is that it can observe frequencies from about 100 MHz to 100 GHz, but it can’t see all those frequencies at once. We break that frequency range up into smaller segments (like 100-300 MHz, 300-400 MHz, and so on) because each frequency range needs its own receiver on the telescope (You can think of the receiver as a radio wave detector). The reason each segment needs its own receiver is because the wavelength varies quite a lot between 100 MHz and 100 GHz, and so you can think of each segment needing its own size wavelength detector. We don’t use the same receiver to detect both meter size waves and centimeter size waves…. that’d be like trying to use an x-ray detector to detect gamma rays!

For pulsars, we use the 350 MHz receiver for two reasons. One: pulsars are much brighter at lower frequencies. Two: Since we are searching for pulsars, we want to cover as much sky as we can in the least amount of time, so we want a big pixel. The thing about this, though, is that when we find a pulsar in our beam, it can be anywhere in the size of the full moon from where our telescope is pointing. So we can point the telescope at one RA and Dec, and if a pulsar is close by (with in the size of the moon), it will show up in our data. That’s why the RA and Dec can vary between what is on the plot and what is in the ATNF catalog.

When we find a pulsar at 350 MHz, since we don’t know its exactly location (it can be anywhere in that full moon range), we try to observe it at a slightly higher frequency. Since the beam gets smaller, we scan the area that was covered by the 350 MHz beam, looking for it. When we find it, we’ve narrowed it down to a smaller region. Then we use the next higher receiver and do the same thing until we get its exact location.

What is a reasonable dispersion measure?

The maximum dispersion measure ranges depending on where the candidate is in the sky. The galaxy is shaped like a disk, and we are about 2/3 from the center of the disk. The DM depends on how much “stuff” is between us and the pulsar. So, if the pulsar is in the plane of the disk, we have to look through a lot of stuff to see it, so the DM can be really high. If the pulsar is outside the plane of the galaxy (like above the disk), then we don’t look through a lot of stuff to see the pulsar, so the maximum DM is much lower. So, what is a maximum dispersion measure depends on where you are looking. To determine what the maximum DM is for your plot, go to the front page of the PSC website and scroll down to where it says “Check the Distance to your Candidate.” Enter the RA, Dec, and DM of your plot. The last sentence will tell you what is a reasonable dispersion measure for any given RA and Dec (it differs for every RA and Dec, so you have to do it for each pointing).

What is reduced chi-squared?

The quantity called “reduced chi-squared” is located in several places on the plots, but most notably next to the time domain subplot, which you grade. Reduced chi-squared, in general, is a measurement of how well your data fit a particular model. If you have a model of something, you know how you expect that something to look and behave. Then, when you go observe that something, you can see how well what you observed matches what you predicted. Reduced chi-squared measures how good that match is. If the data and the model are exactly the same, reduced chi-squared will be exactly 1. The more the data deviate from the model, the larger reduced chi-squared gets.

In the case of the plots, the model we’re using is random noise. We do not want to find random noise! We want to find pulsars. So, for us, a large reduced chi-squared is good because it means that our data do not look like noise. The closer reduced chi-squared is to 1, the more the signal is like noise, and the less likely it is to be a pulsar.

The subplot next to the time domain subplot shows “reduced chi-squared” plotted against “fraction of observation.” As you go from left to right along the “fraction of observation” axis, you are looking at more and more of the data (remember, from above, that the observations have been “folded,” or added together at the guessed period). The more data that have been added together, the more you would expect the signal to look like a pulsar, if it does, in fact, contain a pulsar. So if your plot is showing a pulsar, you would expect reduced chi-squared to get higher and higher as you look at more and more of the data (or go from left to right along the “fraction of observation” axis), because it looks less and less like the model: noise.

If your plot doesn’t contain a pulsar signal, you would expect reduced chi-squared to stay close to one, because folding more and more data does not make a signal pop out, and the data resembles noise, resulting in a reduced chi-squared close to 1.


Pulsar Properties

Why do pulsars slow down over time?

The short answer is: Pulsars slow down because they give off energy and the energy loss causes a loss in rotational energy.

In more detail: The magnetic field is responsible for the radiation that the pulsars give off. The magnetic field accelerates electrons away from the stellar surface, and since the electrons are accelerating, they emit radiation in the form of radio waves. Since the pulsars are radiating away energy, it causes the pulsar to slow down. This mechanism is called “magnetic braking”.

So, for example, with the Crab pulsar…the pulsar radiates away a certain amount of energy over a given period of time because of its magnetic field. That energy is radiated into space, and since the Crab is surrounded by a nebula, the energy heats up the nebula and makes it glow. This match between the predicted energy loss of the Crab pulsar and the amount of energy needed to power the nebula was verification that (at least parts) of the theory of pulsars was correct.

Obviously, not all pulsars are in a nebula. In this case, the energy that the pulsar radiates away just goes out into space. (And, sometimes, eventually reaches Earth.)

Is a pulsar with a higher dispersion measure always farther away than a pulsar with a lower dispersion measure?

Not necessarily. While we often think of dispersion measure as an analogy for distance, that’s not always true. Dispersion measure is a quantification of how much stuff a signal traveled through to get from the pulsar to the telescope. The more stuff, the more the signal was smeared (the larger the difference between the arrival times of higher frequency waves and lower frequency waves), and the larger the dispersion measure.

Do pulsars pulse all the time?

Not always. Pulsars spin very regularly, and their pulses alway comes at the same point in that spin (when a magnetic pole is pointed at Earth). However, pulsars do not always emit radio waves, and do not always have pulses that have the same brightness.

Some pulses may be weaker than others, and some may be stronger, and sometimes, when a pole is pointed at Earth, there may not be radio waves coming from it, so the telescope would not see a pulse. If a pulsar is not emitting radio waves, that is called “nulling.”

Because of nulling and the variations in pulse strength, we need single-pulse plots in addition to prepfold plots. Prepfold plots search for signals that repeat regularly, but what if a pulsar were nulling for 149 of the 150 seconds of observations? What if some pulses are too weak to be detected, so the telescope only catches a few? The pulsar might not pop up in a prepfold search.

In a time domain subplot on the prepfold plot, a nulling pulsar would have gaps in its vertical linearity.

Do pulsars emit other types of light?

Yes! Pulsars can also emit optical light, X rays, and gamma rays, all of which are higher-energy waves.

Can we make pictures of pulsars?

Imagine trying to make a map of Washington, DC…from several thousand light-years away! That’s how hard it would be to make an image of a pulsar. Pulsars are “point sources,” which means that they are smaller than the field-of-view of the GBT (and of every telescope in existence). So while we can see them, since they are smaller than a telescope’s “pixel” (a.k.a. beam, a.k.a. field-of-view), we cannot make a multi-pixel image of them, which is what is required to make a “picture” in the traditional sense.

What does the P-Pdot diagram tell me?

If you know how fast a pulsar is currently spinning (its period) and also how much it is slowing down (its p-dot, or the derivative of its period, which is the change in its period over time), you can find out how that pulsar’s spin properties compare to the spin properties of other pulsars. When pulsars’ periods and period derivatives are plotted against each other, the pulsars tend to fall into several groups. There is a large group of “normal” pulsars, which are losing energy relatively quickly and spin relatively slowly. There is also a large group of pulsars that are spinning very rapidly and losing energy very slowly–these are the millisecond pulsars formed in binary systems.


0 Dislike

Last updated

Comments on this entry

There are no comments on this entry.

Post a comment

Post a comment

Please keep comments relevant to this entry. Comments deemed offensive or inappropriate may be removed.

Debug Console

Close2 MBRequestSessionTimelineDatabase41Events23
Array( ) Array(

Array( ) Array(

Array( ) Array(

Array( TEMP => /var/www/tmp, TMPDIR => /var/www/tmp, TMP => /var/www/tmp, PATH => /usr/lo... Array(
TEMP => /var/www/tmp,
TMPDIR => /var/www/tmp,
TMP => /var/www/tmp,
PATH => /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin,
USER => apache,
HOME => /usr/share/httpd,
SCRIPT_NAME => /index.php,
REQUEST_URI => /kb/usefulresources/pulsar-faq,
REDIRECT_URL => /kb/usefulresources/pulsar-faq,
REMOTE_PORT => 51272,
SCRIPT_FILENAME => /var/www/pulsars/index.php,
SERVER_ADMIN => root@localhost,
CONTEXT_DOCUMENT_ROOT => /var/www/pulsars,
DOCUMENT_ROOT => /var/www/pulsars,
SERVER_SOFTWARE => Apache/2.4.37 (Rocky Linux) OpenSSL/1.1.1k,
HTTP_IF_MODIFIED_SINCE => Sun, 03 Dec 2023 19:58:32 GMT,
HTTP_ACCEPT => text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8,
HTTPS => on,
SCRIPT_URL => /kb/usefulresources/pulsar-faq,
REDIRECT_SCRIPT_URL => /kb/usefulresources/pulsar-faq,
PHP_SELF => /index.php,
REQUEST_TIME_FLOAT => 1719313988.2002,
REQUEST_TIME => 1719313988
separator .
orderBy id
orderDir asc
1 registerIP
2 access
tracker.sid b095a430f90fec13aee4d22295951338
tracker.ssid b095a430f90fec13aee4d22295951338
tracker.rsid b095a430f90fec13aee4d22295951338
session.token f70885e1129d4eb91918356b1d1917c1
  • site 0.043 seconds (+0.043); 2.00 MB (+2.000) - afterInitialise
  • site 0.077 seconds (+0.034); 2.00 MB (0.000) - afterRoute
  • site 0.115 seconds (+0.038); 2.00 MB (0.000) - afterDispatch
  • site 0.122 seconds (+0.007); 2.00 MB (0.000) - beforeRenderModule mod_search (Search)
  • site 0.125 seconds (+0.003); 2.00 MB (0.000) - afterRenderModule mod_search (Search)
  • site 0.125 seconds (+0.000); 2.00 MB (0.000) - beforeRenderModule mod_custom (Footer)
  • site 0.125 seconds (+0.000); 2.00 MB (0.000) - afterRenderModule mod_custom (Footer)
  • site 0.125 seconds (+0.000); 2.00 MB (0.000) - beforeRenderModule mod_custom (Footer social links)
  • site 0.126 seconds (+0.000); 2.00 MB (0.000) - afterRenderModule mod_custom (Footer social links)
  • site 0.126 seconds (+0.000); 2.00 MB (0.000) - beforeRenderModule mod_menu (Main Menu)
  • site 0.139 seconds (+0.013); 2.00 MB (0.000) - afterRenderModule mod_menu (Main Menu)
  • site 0.139 seconds (+0.000); 2.00 MB (0.000) - beforeRenderModule mod_notices (Community Notices)
  • site 0.141 seconds (+0.002); 2.00 MB (0.000) - afterRenderModule mod_notices (Community Notices)
  • site 0.142 seconds (+0.001); 2.00 MB (0.000) - onAfterRender
  • site 0.143 seconds (+0.001); 2.00 MB (0.000) - sessionStore
2 MB

41 Queries Logged: 0.029701471328735 seconds

  1. SELECT data
      FROM `jos_session`
      WHERE `session_id` = '157e31949df60da3b423054ebaeb509d'
      FROM `jos_session`
      WHERE `session_id` = '157e31949df60da3b423054ebaeb509d'
  3. SELECT data
      FROM `jos_session`
      WHERE `session_id` = 'b095a430f90fec13aee4d22295951338'
  4. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_languages'
  5. SELECT session_id
      FROM `jos_session`
      WHERE `session_id` = 'b095a430f90fec13aee4d22295951338'
      LIMIT 1
  6. INSERT INTO `jos_session` (`session_id`,`client_id`,`time`,`ip`)
      VALUES ('b095a430f90fec13aee4d22295951338','0','1719313988','')
  7. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_members'
  8. SELECT, b.title
      FROM `jos_usergroups` AS `a`
      LEFT JOIN jos_usergroups AS b
      ON b.lft <= a.lft
      AND b.rgt >= a.rgt
      WHERE `a`.`id` = '1'
  9. SELECT *
      FROM `jos_viewlevels`
  10. SELECT folder AS type,element AS name,protected,params
      FROM `jos_extensions`
      WHERE `enabled` >= '1'
      AND `type` = 'plugin'
      AND `state` >= '0'
      AND `access` IN ('1','1')
      ORDER BY `ordering` ASC
  11. SELECT,m.menutype,m.title,m.alias,m.note,m.path AS route,,m.type,m.level,m.language,m.browserNav,m.access,m.params,m.home,m.img,m.template_style_id,m.component_id,m.parent_id,e.element AS component
      FROM `jos_menu` AS `m`
      LEFT JOIN jos_extensions AS e
      ON e.extension_id = m.component_id
      WHERE `m`.`published` = '1'
      AND `m`.`parent_id` > '0'
      AND `m`.`client_id` = '0'
      ORDER BY `m`.`lft` ASC
  12. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_kb'
  13. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_tags'
  14. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_categories'
  15. SELECT *
      FROM `jos_categories`
      WHERE `jos_categories`.`extension` = 'com_kb'
      AND `jos_categories`.`alias` = 'usefulresources'
      AND `jos_categories`.`published` = '1'
  16. SELECT *
      FROM `jos_categories`
      WHERE `jos_categories`.`extension` = 'com_kb'
      AND `jos_categories`.`alias` = 'pulsar-faq'
      AND `jos_categories`.`published` = '1'
  17. SELECT,jos_template_styles.home,jos_template_styles.template,jos_template_styles.params,jos_extensions.protected
      FROM `jos_template_styles`
      INNER JOIN jos_extensions
      ON jos_extensions.element = jos_template_styles.template
      WHERE `jos_template_styles`.`client_id` = '0'
      AND `jos_extensions`.`enabled` = '1'
      AND `jos_extensions`.`type` = 'template'
      AND jos_extensions.`client_id` = `jos_template_styles`.`client_id`
      ORDER BY `home` DESC
  18. SELECT *
      FROM `jos_kb_articles`
      WHERE `jos_kb_articles`.`alias` = 'pulsar-faq'
      AND `jos_kb_articles`.`category` = '35'
  19. SELECT *
      FROM `jos_categories`
      WHERE `jos_categories`.`id` = '35'
  20. SELECT jos_tags_object.label,jos_tags.*
      FROM `jos_tags`
      INNER JOIN jos_tags_object
      ON jos_tags_object.tagid =
      WHERE `jos_tags_object`.`tbl` = 'kb'
      AND `jos_tags_object`.`objectid` = '56'
      AND `jos_tags`.`admin` NOT IN ('1')
      GROUP BY jos_tags_object.label,
  21. SELECT category,count(*) AS articles
      FROM `jos_kb_articles`
      WHERE `jos_kb_articles`.`state` = '1'
      AND `jos_kb_articles`.`access` IN ('1','1')
      GROUP BY category
  22. SELECT *
      FROM `jos_categories`
      WHERE `jos_categories`.`extension` = 'com_kb'
      AND `jos_categories`.`published` = '1'
      AND `jos_categories`.`access` IN ('1','1')
      AND `jos_categories`.`parent_id` = '1'
      ORDER BY `title` ASC
  23. SELECT *
      FROM `jos_categories`
      WHERE `jos_categories`.`parent_id` = '34'
      AND `jos_categories`.`published` = '1'
      AND `jos_categories`.`access` IN ('1','1')
  24. SELECT *
      FROM `jos_categories`
      WHERE `jos_categories`.`parent_id` = '19'
      AND `jos_categories`.`published` = '1'
      AND `jos_categories`.`access` IN ('1','1')
  25. SELECT *
      FROM `jos_categories`
      WHERE `jos_categories`.`parent_id` = '18'
      AND `jos_categories`.`published` = '1'
      AND `jos_categories`.`access` IN ('1','1')
  26. SELECT *
      FROM `jos_categories`
      WHERE `jos_categories`.`parent_id` = '31'
      AND `jos_categories`.`published` = '1'
      AND `jos_categories`.`access` IN ('1','1')
  27. SELECT *
      FROM `jos_categories`
      WHERE `jos_categories`.`parent_id` = '32'
      AND `jos_categories`.`published` = '1'
      AND `jos_categories`.`access` IN ('1','1')
  28. SELECT *
      FROM `jos_categories`
      WHERE `jos_categories`.`parent_id` = '33'
      AND `jos_categories`.`published` = '1'
      AND `jos_categories`.`access` IN ('1','1')
  29. SELECT *
      FROM `jos_categories`
      WHERE `jos_categories`.`parent_id` = '35'
      AND `jos_categories`.`published` = '1'
      AND `jos_categories`.`access` IN ('1','1')
  30. SELECT *
      FROM `jos_kb_comments`
      WHERE `jos_kb_comments`.`entry_id` = '56'
      AND `jos_kb_comments`.`state` IN ('1','3')
  31. SELECT *
      FROM `jos_kb_comments`
      WHERE `jos_kb_comments`.`id` = '0'
  32. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_users'
  33. SELECT,m.title,m.module,m.position,m.content,m.showtitle,m.params,mm.menuid,e.protected
      FROM `jos_modules` AS `m`
      LEFT JOIN jos_modules_menu AS mm
      ON mm.moduleid =
      LEFT JOIN jos_extensions AS e
      ON e.element = m.module
      AND e.client_id = m.client_id
      WHERE `m`.`published` = '1'
      AND `e`.`enabled` = '1'
      AND (`m`.`publish_up` IS NULL OR `m`.`publish_up` <= '2024-06-25 11:13:08' )
      AND (`m`.`publish_down` IS NULL OR `m`.`publish_down` >= '2024-06-25 11:13:08' )
      AND `m`.`access` IN ('1','1')
      AND `m`.`client_id` = '0'
      AND (`mm`.`menuid` = '82' OR `mm`.`menuid` <= '0' )
      ORDER BY `m`.`position` ASC,`m`.`ordering` ASC
  34. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_search'
  35. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_content'
  36. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_courses'
  37. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_events'
  38. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_newsletter'
  39. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_psrsearch'
  40. SELECT publish_up, publish_down
      FROM `jos_modules`
      WHERE id=45
  41. UPDATE `jos_session`
      SET `data` = '__default|a:10:{s:15:\"session.counter\";i:1;s:19:\"session.timer.start\";i:1719313988;s:18:\"session.timer.last\";i:1719313988;s:17:\"\";i:1719313988;s:8:\"registry\";O:23:\"Hubzero\\Config\\Registry\":2:{s:7:\"\0*\0data\";O:8:\"stdClass\":1:{s:1:\"0\";s:7:\"session\";}s:9:\"separator\";s:1:\".\";}s:4:\"user\";C:17:\"Hubzero\\User\\User\":22:{a:1:{s:5:\"guest\";b:1;}}s:11:\"tracker.sid\";s:32:\"b095a430f90fec13aee4d22295951338\";s:12:\"tracker.ssid\";s:32:\"b095a430f90fec13aee4d22295951338\";s:12:\"tracker.rsid\";s:32:\"b095a430f90fec13aee4d22295951338\";s:13:\"session.token\";s:32:\"f70885e1129d4eb91918356b1d1917c1\";}',`time` = '1719313988',`ip` = ''
      WHERE `session_id` = 'b095a430f90fec13aee4d22295951338'
  • onAfterInitialise Method plgSystemP3p::onAfterInitialise /core/plugins/system/p3p/p3p.php:21
  • onAfterInitialise Method plgSystemRemember::onAfterInitialise /core/plugins/system/remember/remember.php:20
  • onAfterInitialise Method plgSystemHubzero::onAfterInitialise /core/plugins/system/hubzero/hubzero.php:21
  • onAfterInitialise Method plgSystemXFeed::onAfterInitialise /core/plugins/system/xfeed/xfeed.php:21
  • onAfterInitialise Method plgSystemSupergroup::onAfterInitialise /core/plugins/system/supergroup/supergroup.php:113
  • onAfterInitialise Method plgSystemReferrerpolicy::onAfterInitialise /core/plugins/system/referrerpolicy/referrerpolicy.php:21
  • onAfterRoute Method plgSystemJquery::onAfterRoute /core/plugins/system/jquery/jquery.php:21
  • onAfterRoute Method plgSystemSpamjail::onAfterRoute /core/plugins/system/spamjail/spamjail.php:21
  • onAfterRoute Method plgSystemIncomplete::onAfterRoute /core/plugins/system/incomplete/incomplete.php:21
  • onAfterRoute Method plgSystemUnconfirmed::onAfterRoute /core/plugins/system/unconfirmed/unconfirmed.php:21
  • onAfterRoute Method plgSystemUnapproved::onAfterRoute /core/plugins/system/unapproved/unapproved.php:21
  • onAfterRoute Method plgSystemPassword::onAfterRoute /core/plugins/system/password/password.php:21
  • onContentPrepare Method plgContentLoadmodule::onContentPrepare /core/plugins/content/loadmodule/loadmodule.php:35
  • onContentPrepare Method plgContentEmailcloak::onContentPrepare /core/plugins/content/emailcloak/emailcloak.php:25
  • onContentPrepare Method plgContentPagebreak::onContentPrepare /core/plugins/content/pagebreak/pagebreak.php:35
  • onContentPrepare Method plgContentXhubtags::onContentPrepare /core/plugins/content/xhubtags/xhubtags.php:25
  • onContentPrepare Method plgContentFormatwiki::onContentPrepare /core/plugins/content/formatwiki/formatwiki.php:63
  • onContentPrepare Method plgContentFormathtml::onContentPrepare /core/plugins/content/formathtml/formathtml.php:105
  • onContentPrepare Method plgContentExternalhref::onContentPrepare /core/plugins/content/externalhref/externalhref.php:41
  • onAfterDispatch Method plgSystemMobile::onAfterDispatch /core/plugins/system/mobile/mobile.php:22
  • onAfterDispatch Method plgSystemDebug::onAfterDispatch /core/plugins/system/debug/debug.php:60
  • onAfterDispatch Method PlgSystemHighlight::onAfterDispatch /core/plugins/system/highlight/highlight.php:25
  • onAfterRender Method plgSystemSef::onAfterRender /core/plugins/system/sef/sef.php:21