[education/kstars] doc: Fix minor typos
Git commit 213420d9005ba2745e31a5e2eb4ce2143f5571d3 by Yuri Chornoivan. Committed on 01/04/2024 at 12:57. Pushed by yurchor into branch 'master'. Fix minor typos M +2-2doc/ekos-focus.docbook https://invent.kde.org/education/kstars/-/commit/213420d9005ba2745e31a5e2eb4ce2143f5571d3 diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook index 85703a8ede..976ab2f61e 100644 --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -236,7 +236,7 @@ When a new Optical Train is created, Focus will attempt to default parameters from other, similar Optical Trains. The attributes that must match for this are the Focuser and -the scope type. If this is the first train for the seclected Focuser and scope type then +the scope type. If this is the first train for the selected Focuser and scope type then default parameters are created. It is recommended to use the @@ -1034,7 +1034,7 @@ Average HFR check: Similar idea to Average Over but in this case -it it the HFR Check datapoint that is averaged over the selected number of frames. In addition, if the +it is the HFR Check datapoint that is averaged over the selected number of frames. In addition, if the Algorithm is Linear 1 Pass then the last datapoint of an Autofocus run, which is the in-focus datapoint, is also averaged over this number of frames. Set a value of 1 to start. This can be increased if there are issues with HFR Check Autofocus runs being triggered by outlying datapoints when the HFR Check runs.
[education/kstars] doc: Fix minor typos
Git commit d8ea2a0546ed7ad7a5a80efcc077b90b4572af39 by Yuri Chornoivan. Committed on 08/02/2024 at 07:23. Pushed by yurchor into branch 'master'. Fix minor typos M +5-5doc/ekos-focus.docbook https://invent.kde.org/education/kstars/-/commit/d8ea2a0546ed7ad7a5a80efcc077b90b4572af39 diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook index f306a3e0e3..4cc44180b1 100644 --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -609,7 +609,7 @@ -Mask Section Paramters: +Mask Section Parameters: These controls relate to Masking Options to be used when in Full Field mode. The effect of Masking Options can be seen in the @@ -1024,7 +1024,7 @@ moves out to take its first datapoint, an exposure of 2s * 4 = 8s is used. On each successive datapoint the exposure is reduced down to 2s around the point of optimum focus. As the focuser moves through focus, so the exposure is scaled upwards to 8s for the last datapoint. - The purpose of this feature is to increase the brighness of out of focus datapoints which will be dimmer than + The purpose of this feature is to increase the brightness of out of focus datapoints which will be dimmer than in-focus datapoints and therefore harder for star detection to resolve from the background noise. This feature assumes Autofocus is run from near to optimum focus. @@ -1252,7 +1252,7 @@ - Focus CFZ Parameters:. +Focus CFZ Parameters: @@ -1274,9 +1274,9 @@ Focus Mechanics It is necessary to specify the Step Size parameter which specifies in microns how far one tick -moves the focal plane. For refractors there is uaually a 1-to-1 relationship between moving the focuser which moves the +moves the focal plane. For refractors there is usually a 1-to-1 relationship between moving the focuser which moves the telescope draw-tube mechanism and the focal plane movement. For other types of telescope the relationship is likely to be -more complex. Refer to details of your telescope / manufacturer for this inmformation. +more complex. Refer to details of your telescope / manufacturer for this information. The following algorithms are available:
[education/kstars] doc: Fix minor typos
Git commit 8000761333e5751f749ba84372aacb420f1b7373 by Yuri Chornoivan. Committed on 25/12/2023 at 07:48. Pushed by yurchor into branch 'master'. Fix minor typos M +1-1doc/ekos-capture.docbook https://invent.kde.org/education/kstars/-/commit/8000761333e5751f749ba84372aacb420f1b7373 diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook index 3779c182e9..597cd5bf25 100644 --- a/doc/ekos-capture.docbook +++ b/doc/ekos-capture.docbook @@ -370,7 +370,7 @@ -The overlay options button opens a dialog that allows arbitary and flexible creation of ellipses (including circles), rectangles and lines, as well as anchor points which act as global drawing offsets. Each defined element has it's own size, offset, repetition, thickness and color (including transparency). +The overlay options button opens a dialog that allows arbitrary and flexible creation of ellipses (including circles), rectangles and lines, as well as anchor points which act as global drawing offsets. Each defined element has its own size, offset, repetition, thickness and color (including transparency).
[education/kstars] doc: Fix minor typos
Git commit 16796ae7aa45f7dcd7e975cae605e3ec86ae9f0b by Yuri Chornoivan. Committed on 06/12/2023 at 08:06. Pushed by yurchor into branch 'master'. Fix minor typos M +1-1doc/index.docbook https://invent.kde.org/education/kstars/-/commit/16796ae7aa45f7dcd7e975cae605e3ec86ae9f0b diff --git a/doc/index.docbook b/doc/index.docbook index b5d78d59ab..6b7efa7144 100644 --- a/doc/index.docbook +++ b/doc/index.docbook @@ -247,7 +247,7 @@ For students and teachers, it supports adjustable simulation speeds in order to - Ekos is a complete astrophotography solution that provides everything needed for automated or manual deep-sky imaging. It can control all INDI devices including numerous telescopes, CCD and CMOS astronomy cameras, DSLRs, focusers, filters, rotators, domes and a lot more. Ekos supports highly accurate tracking using online and offline astrometry solvers, autofocus and autoguiding capabilities, and capture of single or multiple images using its powerful built in scheduler. It integrates well with the skymap, and FITS Viewer. It also has tools for polar alignment and measuing optical aberrations. + Ekos is a complete astrophotography solution that provides everything needed for automated or manual deep-sky imaging. It can control all INDI devices including numerous telescopes, CCD and CMOS astronomy cameras, DSLRs, focusers, filters, rotators, domes and a lot more. Ekos supports highly accurate tracking using online and offline astrometry solvers, autofocus and autoguiding capabilities, and capture of single or multiple images using its powerful built-in scheduler. It integrates well with the skymap, and FITS Viewer. It also has tools for polar alignment and measuring optical aberrations.
[education/kstars] doc: Fix minor typos
Git commit 0a8c955febd324a24ccd9ced549017cbebefb472 by Yuri Chornoivan. Committed on 05/12/2023 at 14:22. Pushed by yurchor into branch 'master'. Fix minor typos M +1-1doc/ekos.docbook M +1-1doc/obsplanner.docbook https://invent.kde.org/education/kstars/-/commit/0a8c955febd324a24ccd9ced549017cbebefb472 diff --git a/doc/ekos.docbook b/doc/ekos.docbook index 89a2eeecf7..794a3dd486 100644 --- a/doc/ekos.docbook +++ b/doc/ekos.docbook @@ -35,7 +35,7 @@ -Measure Correct Polar Alignment errors using astromety.net solver. +Measure Correct Polar Alignment errors using astrometry.net solver. diff --git a/doc/obsplanner.docbook b/doc/obsplanner.docbook index 54384bdc08..e9f5e3023a 100644 --- a/doc/obsplanner.docbook +++ b/doc/obsplanner.docbook @@ -138,7 +138,7 @@ it could be a bit more detailed. Here you can see the same categories of objects - You can choose the treshold of magnitude for the objects to be shown. In astronomy, absolute magnitude (also known as absolute visual magnitude when measured in the standard V photometric band) measures a celestial objects intrinsic brightness. + You can choose the threshold of magnitude for the objects to be shown. In astronomy, absolute magnitude (also known as absolute visual magnitude when measured in the standard V photometric band) measures a celestial objects intrinsic brightness.
[education/kstars] doc: Fix minor typos
Git commit 44e5086501f8c6513bfd00e321b42d4c5ef0b46d by Yuri Chornoivan. Committed on 02/12/2023 at 22:23. Pushed by yurchor into branch 'master'. Fix minor typos M +4-4doc/ekos-capture.docbook https://invent.kde.org/education/kstars/-/commit/44e5086501f8c6513bfd00e321b42d4c5ef0b46d diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook index 5f816339a7..3f48da3f16 100644 --- a/doc/ekos-capture.docbook +++ b/doc/ekos-capture.docbook @@ -520,12 +520,12 @@ Approaches to imaging can vary greatly in the selection of exposure times, and n Sky Quality: The Sky Quality selector sets the measurement of the magnitude per square arc-second of the background sky. The range for Sky Quality is from 22 for the darkest skies, to 16 for the brightest (most light-polluted) skies. The magnitude scale is non-linear; it is a logarithmic scale based on the 5th root of 100. So 5 steps on the scale represent a change in brightness by a factor of 100. (A Sky Quality of 17 is 100 times as bright as a Sky Quality of 22. Each full integer step on the scale is a change by a factor of approximately 2.512.). https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia Sky Brightness -https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia Light Pollution +https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia Light Pollution All light scattered in the background sky is considered to be light pollution regardless of its source, so the effects of moonlight should be considered as "natural" light pollution. But weather conditions can also impact Sky Quality, as humidity or cloud cover can reflect and scatter any source of light through the atmosphere - A https://en.wikipedia.org/wiki/Sky_quality_meter;>Sky Quality Meter (SQM) - can provide the most accurate reading of sky quality if used during an imaging session, but an estimated value from sky quality surveys may also be found on the web at sites such as https://www.lightpollutionmap.info/;>www.lightpollutionmap.info or https://clearoutside.com/;>www.clearoutside.com. But these on-line sources for estimated light pollution generally do not account for the effects of moonlight or local weather conditions. So the values from light pollution web sites should only be considered as a “best case scenario” for a cloudless night during a new moon. + A https://en.wikipedia.org/wiki/Sky_quality_meter;>Sky Quality Meter (SQM) + can provide the most accurate reading of sky quality if used during an imaging session, but an estimated value from sky quality surveys may also be found on the web at sites such as https://www.lightpollutionmap.info/;>www.lightpollutionmap.info or https://clearoutside.com/;>www.clearoutside.com. But these on-line sources for estimated light pollution generally do not account for the effects of moonlight or local weather conditions. So the values from light pollution web sites should only be considered as a “best case scenario” for a cloudless night during a new moon. If a light pollution map value is used for the input value of SQM, but imaging will be performed with a partial moon, then a decrease in the input of the SQM value should be applied in the calculator. Moonlight can be overwhelming; at a location where a light pollution map showed an SQM value of 19.63. An SQM reading was made on a night with a waxing crescent, shortly before half-moon, (moon age 5.4, and KStars moon magnitude = -10). The SQM reading at zenith showed the sky to be much brighter with measured value of 18.48. A reading taken on a night with a waxing gibbous, shortly before a full moon, (moon age 12.4, and KStars moon magnitude = -12). The SQM reading at zenith showed a measured SQM value of 15.95. The value of Sky Quality has a drastic impact on the calculated exposure because of the logarithmic scale involved. An image taken from a location with heavy light pollution (a low sky quality value), especially when filtering is not applied, may result in a very short exposure time to prevent light pollution from overwhelming the target signal. An image taken from a location with very little light pollution (a high Sky Quality value) may result in an sub-exposure time of several hours. @@ -559,7 +559,7 @@ Even within the bands that filters are intended to pass, filters are not 100% ef Camera sensors are one of two types: "Charge Coupled Device" (CCD) or "Complementary Metal-Oxide Semiconductor" (CMOS). For the exposure calculation the main difference between these sensor types is that CCD sensors do not have a variable gain setting that would impact the read noise; so a CCD sensor will have a single constant value for
[education/kstars] doc: Fix minor typos
Git commit 397fcc66b4cb982045868a16c6d5d40bbfda5401 by Yuri Chornoivan. Committed on 02/12/2023 at 22:18. Pushed by yurchor into branch 'master'. Fix minor typos M +2-2doc/ekos-focus.docbook https://invent.kde.org/education/kstars/-/commit/397fcc66b4cb982045868a16c6d5d40bbfda5401 diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook index 10d53f6ef0..459e9a4d46 100644 --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -2162,7 +2162,7 @@ autofocus-(datetime).txt files from a few nights of observing into a spreadsheet and graph focus position against temperature for each filter. Review the data and remove any outliers and plot a line of best fit. Use the line to get Ticks / °C. If you intend to adapt for altitude as well as temperature, then it would be better to use a -set of data at similar altitude when calibrating temperature. Then its possible to calculate the effect of Temperature and +set of data at similar altitude when calibrating temperature. Then it's possible to calculate the effect of Temperature and remove this from the data when calculating the effect of Altitude. You will need to ensure that your focus position is repeatable at the same temperature and altitude and that there @@ -2532,7 +2532,7 @@ some calculations may not be performed. If the Centre tile is excluded, no calculations can be performed. -Note that whilst its possible to exclude tiles and still get calculated values, if the data +Note that whilst it's possible to exclude tiles and still get calculated values, if the data is poor quality then it is recommended to rerun Aberration Inspector rather than persist with poor quality data.
[education/kstars] doc: Fix minor typos
Git commit 41cb8e87b737a6e30234d78d2e2bfeb21c2b83bd by Yuri Chornoivan. Committed on 02/12/2023 at 19:28. Pushed by yurchor into branch 'master'. Fix minor typos M +1-1doc/commands.docbook M +2-2doc/ekos-capture.docbook M +1-1doc/ekos-focus.docbook M +1-1doc/timezones.docbook https://invent.kde.org/education/kstars/-/commit/41cb8e87b737a6e30234d78d2e2bfeb21c2b83bd diff --git a/doc/commands.docbook b/doc/commands.docbook index 8560d8da73..721a4cef01 100644 --- a/doc/commands.docbook +++ b/doc/commands.docbook @@ -17,7 +17,7 @@ File Open Image... -Open a image in the FITS Viewer tool. +Open an image in the FITS Viewer tool. diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook index 80c67d6a10..6610f9cb33 100644 --- a/doc/ekos-capture.docbook +++ b/doc/ekos-capture.docbook @@ -646,7 +646,7 @@ The value of image stacking is that as images are stacked, the accumulation of e Table: A table provides details for stacking based upon the number of hours planned for imaging. -The table provides a quick reference for finding the approximate number of sub-exposures that might be completed for a given number of hours in a imaging session. But some functions that consume time are not included in this time calculation. For example, USB based cameras typically take some time for data transmission, or if the user has selected automatic dithering, additional time will be consumed in the imaging process, which is not included in this time calculation. +The table provides a quick reference for finding the approximate number of sub-exposures that might be completed for a given number of hours in an imaging session. But some functions that consume time are not included in this time calculation. For example, USB based cameras typically take some time for data transmission, or if the user has selected automatic dithering, additional time will be consumed in the imaging process, which is not included in this time calculation. The far right column of the table shows the calculated time/noise ratio of the integrated (stacked) image that would be produced. @@ -669,7 +669,7 @@ Depending on the various inputs and imaging conditions, the potential quality of -Part of the value of using a Time/Noise ratio as the input for the calculation of the required number of sub-exposures is that it should tend to compensate for the differences in relative noise for sub-exposures of various lengths. A shorter sub-exposure would have a lower time/noise ratio, so it has less capacity to improve a integrated image. Therefore, a disproportionately higher number of short exposures are needed to achieve a given time/noise ratio in an integrated image. +Part of the value of using a Time/Noise ratio as the input for the calculation of the required number of sub-exposures is that it should tend to compensate for the differences in relative noise for sub-exposures of various lengths. A shorter sub-exposure would have a lower time/noise ratio, so it has less capacity to improve an integrated image. Therefore, a disproportionately higher number of short exposures are needed to achieve a given time/noise ratio in an integrated image. As an example, consider the calculation of the number of sub-exposures required when two sub-exposures times were compared: a 300 second sub-exposure vs a 30 second sub-exposure. The 300 second sub-exposure had a calculated noise of 22.1, resulting in a sub-exposure time/noise ratio of 13.6. When the 'noise increase %' is raised to force the exposure time down to 30 seconds, we see a calculated noise of 9.47, resulting in a much lower sub-exposure time/noise ratio of 3.2. The 300 second exposure is of significantly higher potential quality than the 30 second exposure. We will demand the default time/noise ratio of 80 for integration in both of these cases. diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook index 0e4292fd7f..10d53f6ef0 100644 --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -2400,7 +2400,7 @@ will vary by equipment and must be discovered by the user by trial and error. Always follow the recommendations of the tilt / backfocus device manufacturer. -Each time Aberration Inspector is run it lauches a new dialog with the run number appended to the title. +Each time Aberration Inspector is run it launches a new dialog with the run number appended to the title. This way several runs can be performed and the results compared. Note, however, that the dialog holds a lot of data (roughly 10x the amount of a standard Autofocus run). The system resources associated with this are released when the dialog is closed. For this reason on lower powered machines, once the tool has been used, it is recommended diff --git
[education/kstars] doc: Fix minor typos
Git commit 187dcff04e640624de09bca1e8926f4138161191 by Yuri Chornoivan. Committed on 02/12/2023 at 07:50. Pushed by yurchor into branch 'master'. Fix minor typos M +5-5doc/ekos-focus.docbook https://invent.kde.org/education/kstars/-/commit/187dcff04e640624de09bca1e8926f4138161191 diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook index 048c1ade91..0e4292fd7f 100644 --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -2396,13 +2396,13 @@ Repeat the above process until the limit of sensitivity of the equipment is reached. -Note the amount of adjustment, e.g. how far to turn bolts, and the sense, counterwise or counter-clockwise, +Note the amount of adjustment, e.g. how far to turn bolts, and the sense, clockwise or counter-clockwise, will vary by equipment and must be discovered by the user by trial and error. Always follow the recommendations of the tilt / backfocus device manufacturer. Each time Aberration Inspector is run it lauches a new dialog with the run number appended to the title. This way several runs can be performed and the results compared. Note, however, that the dialog holds a lot of -data (roughtly 10x the amount of a standard Autofocus run). The system resources associated with this are released +data (roughly 10x the amount of a standard Autofocus run). The system resources associated with this are released when the dialog is closed. For this reason on lower powered machines, once the tool has been used, it is recommended to close all Aberration Inspector dialogs before imaging. @@ -2650,7 +2650,7 @@ - Slice: A 2D slice throught the 3D graphic is displayed. + Slice: A 2D slice through the 3D graphic is displayed. @@ -2684,9 +2684,9 @@ -The 3D graphic is not essential to using Aberration Inspector. All relevent information is displayed in the +The 3D graphic is not essential to using Aberration Inspector. All relevant information is displayed in the Table and Results -sections of the dialog. Its purpose is to aid the user in undertanding Aberration Inspector and to orient themselves +sections of the dialog. Its purpose is to aid the user in understanding Aberration Inspector and to orient themselves with the information the tool provides.
[education/kstars] doc: Fix minor typos
Git commit 323adaebb6b30b3b11428819a03dd1f5c92f0644 by Yuri Chornoivan. Committed on 30/11/2023 at 07:16. Pushed by yurchor into branch 'master'. Fix minor typos M +7-7doc/ekos-capture.docbook https://invent.kde.org/education/kstars/-/commit/323adaebb6b30b3b11428819a03dd1f5c92f0644 diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook index bbbf7ba139..4237c7268c 100644 --- a/doc/ekos-capture.docbook +++ b/doc/ekos-capture.docbook @@ -510,7 +510,7 @@ The implementation of this process does not consider the strength (magnitude or flux) of the intended target, nor does it consider other factors which may cause an astrophotographer to choose a alternate sub-exposure time. These other factors may include: the storage requirements and extended post-processing time for a large number of short exposures, the impacts of external factors that might occur in very long exposures, such as tracking / guiding performance, changes in weather conditions which may disrupt seeing conditions, intrusions from air traffic or passing satellites. -Approaches to imaging can vary greatly in the selection of exposure times, and number of sub-exposures used for integration. A well accepted approach for imaging deep-sky objects utilizes long exposures, requires good guiding, good to excellent seeing conditions, and would typically employ filtering to reduce the effects of light polution. At the other extreme are approaches such as speckle imaging techniques (commonly 'lucky imaging'), which utilize many hundreds to many thousands of extremely short exposures in an attempt to eliminate the effects of light pollution, poor seeing conditions, and poor guiding. Choices made for values of certain inputs to the exposure calculator will vary depending upon which imaging approach is being employed. +Approaches to imaging can vary greatly in the selection of exposure times, and number of sub-exposures used for integration. A well accepted approach for imaging deep-sky objects utilizes long exposures, requires good guiding, good to excellent seeing conditions, and would typically employ filtering to reduce the effects of light pollution. At the other extreme are approaches such as speckle imaging techniques (commonly 'lucky imaging'), which utilize many hundreds to many thousands of extremely short exposures in an attempt to eliminate the effects of light pollution, poor seeing conditions, and poor guiding. Choices made for values of certain inputs to the exposure calculator will vary depending upon which imaging approach is being employed. @@ -522,10 +522,10 @@ Approaches to imaging can vary greatly in the selection of exposure times, and n The range for Sky Quality is from 22 for the darkest skies, to 16 for the brightest (most light-polluted) skies. The magnitude scale is non-linear; it is a logarithmic scale based on the 5th root of 100. So 5 steps on the scale represent a change in brightness by a factor of 100. (A Sky Quality of 17 is 100 times as bright as a Sky Quality of 22. Each full integer step on the scale is a change by a factor of approximately 2.512.). https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia Sky Brightness https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia Light Pollution - All light scattered in the backgound sky is considered to be light pollution regardless of its source, so the effects of moonlight should be considered as "natural" light pollution. But weather conditions can also impact Sky Quality, as humidity or cloud cover can reflect and scatter any source of light through the atmosphere + All light scattered in the background sky is considered to be light pollution regardless of its source, so the effects of moonlight should be considered as "natural" light pollution. But weather conditions can also impact Sky Quality, as humidity or cloud cover can reflect and scatter any source of light through the atmosphere A https://en.wikipedia.org/wiki/Sky_quality_meter;>Sky Quality Meter (SQM) - can provide the most accurate reading of sky quality if used during an imaging session, but an estimated value from sky quality surveys may also be found on the web at sites such as https://www.lightpollutionmap.info/;>www.lightpollutionmap.info or https://clearoutside.com/;>www.clearoutside.com. But these on-line sources for estimated light pollution genearrly do not account for the effects of moonlight or local weather conditions. So the values from light pollution web sites should only be considered as a “best case scenario” for a cloudless night during a new moon. + can provide the most accurate reading of sky quality if used during an imaging session,
[education/kstars] doc: Fix minor typos
Git commit a56cdba513c6881d3e92a03c7565c055069510f7 by Yuri Chornoivan. Committed on 21/10/2023 at 07:51. Pushed by yurchor into branch 'master'. Fix minor typos M +2-2doc/fitsviewer.docbook https://invent.kde.org/education/kstars/-/commit/a56cdba513c6881d3e92a03c7565c055069510f7 diff --git a/doc/fitsviewer.docbook b/doc/fitsviewer.docbook index a26640bd4..bb2157115 100644 --- a/doc/fitsviewer.docbook +++ b/doc/fitsviewer.docbook @@ -162,7 +162,7 @@ To open a FITS file, select the File -Near the bottom of the window are controls for stretching the image and displaying its histogram. They are discribed below from left to right. +Near the bottom of the window are controls for stretching the image and displaying its histogram. They are described below from left to right. Enable Stretching: On the very left of this display is a button that enables or disables stretching. Shadow Value: The value below which pixels are displayed as black can be manually entered (scale is 0 to 1.0, even for integer pixel values). @@ -295,7 +295,7 @@ To open a FITS file, select the File Solve Button. Pressing this button starts plate solving. When the system is plate solving, the button becomes an abort button. -Scale: Checking the Use Scale checkbox constains the solver to use approximately the pixel or image scale given. The scale is entered in the box and the units for the scale can be chosen from image width in degrees, image width in arc-minutes, and arc-seconds per pixel. When a solve successfully completes, it replaces the value in the box with solution's scale. +Scale: Checking the Use Scale checkbox contains the solver to use approximately the pixel or image scale given. The scale is entered in the box and the units for the scale can be chosen from image width in degrees, image width in arc-minutes, and arc-seconds per pixel. When a solve successfully completes, it replaces the value in the box with solution's scale. Position: Checking the Use Position checkbox constains the solver to search near the RA and DEC coordinates given. The extent of the search is given by the user in the Radius box in degrees. Note that RA is input in hours-minutes-seconds, e.g. 13h, and DEC is input in degrees-minutes-seconds, e.g. 85. When a solve successfully completes, it replaces the value in the RA and DEC boxes with solution's coordinates. In addition it fills in the Angle field with the solutions angle value in degrees. Use SkyMap Position: There is a button just below the Use Position checkbox that fills in RA and DEC boxes with the current center of the SkyMap display. Profile: The Profile menu selects which StellarSolver preset, among those used in the Ekos Align module, should be used for plate solving. This is further discussed below.
[education/kstars] doc: Fix minor typos
Git commit 047e68676f04d53ac813a3e25c40f9e965dcc761 by Yuri Chornoivan. Committed on 17/08/2023 at 07:55. Pushed by yurchor into branch 'master'. Fix minor typos M +1-1doc/config.docbook https://invent.kde.org/education/kstars/-/commit/047e68676f04d53ac813a3e25c40f9e965dcc761 diff --git a/doc/config.docbook b/doc/config.docbook index 9ecb8e4b2..9e5b759bf 100644 --- a/doc/config.docbook +++ b/doc/config.docbook @@ -1201,7 +1201,7 @@ Start KStars once you have images in the imageOverlays directory. If you then go To prepare your images for display, you need to plate-solve the images (one time only). To do this, find an image in the table, click on its filename, and then click Solve below the table. The Solve button's label should switch to Cancel during the solve, and then when completed successfully, the solved parameters are displayed in the table and the status is changed to "OK". A successful plate-solve's information is stored in the user database so that solving doesn't need to be repeated. The solved image should from then on appear in its proper position in the SkyMap. You can plate-solve multiple images in a single operation by clicking on the first image's filename, then shift clicking on another filename. All the image files between the filenames should be selected. Then clicking Solve will attempt to solve them all. However, KStars will not attempt to plate-solve images whose status is "OK", it will skip those images. (If you wish to re-plate-solve images with status "OK", then manually change their status to "Unprocessed" and click "Solve"). It is possible that if you select several images, a few of them will not be successfully solved. -Plate solving these images can sometimes be difficult. That is because at this point the system has no information as to the scale or position to look, and thus it is a blind solve. To improve your chance for success, you can enter an approxiate RA/DEC center sky position into the RA and DEC columns for the row you are trying to solve. You can also add an image scale, in arcseconds-per-pixel. You can add a default scale to the right of the Solve button in the box labelled Default a-s/px so that all solving attempts use this scale by default. You can also add a scale directly into the table-row-column, which would override the default. You can choose which StellarSolver profile the solver uses (these profiles can be edited in Ekos' align tab). Finally, you can adjust the solver's Timeout in seconds. +Plate solving these images can sometimes be difficult. That is because at this point the system has no information as to the scale or position to look, and thus it is a blind solve. To improve your chance for success, you can enter an approximate RA/DEC center sky position into the RA and DEC columns for the row you are trying to solve. You can also add an image scale, in arcseconds-per-pixel. You can add a default scale to the right of the Solve button in the box labeled Default a-s/px so that all solving attempts use this scale by default. You can also add a scale directly into the table-row-column, which would override the default. You can choose which StellarSolver profile the solver uses (these profiles can be edited in Ekos' align tab). Finally, you can adjust the solver's Timeout in seconds. If you have problematic images that won't solve, you can still display them by manually entering the values (that the solver didn't find) into the table. They are the RA, DEC, arcsecond-per-pixel, orientation angle, and east-to-the-right (or West-to-the-right) settings. Once you have done that, you can then change the status to "OK" and KStars will save these values to the user database as if they had been automatically solved.
[education/kstars] doc: Fix minor typos
Git commit 81129ae4f7773d05c351a863971613bcbc870d6e by Yuri Chornoivan. Committed on 28/07/2023 at 14:15. Pushed by yurchor into branch 'master'. Fix minor typos M +3-3doc/ekos-focus.docbook https://invent.kde.org/education/kstars/-/commit/81129ae4f7773d05c351a863971613bcbc870d6e diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook index be73cc2c2..72c8cabc7 100644 --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -1702,7 +1702,7 @@ If the Adapt Focus box is checked, the AF Runs are updated for Adaptive Focus. See the - Adaptive Focus section for more details on the theory of Adaptive Focus.The first AF run + Adaptive Focus section for more details on the theory of Adaptive Focus. The first AF run (in this example AF Run 1 on Lum) is the basis for the Adaptations. So the temperature and altitude of AF Run 1 on Lum is used as the basis for all the other AF Runs and the data is adapted back to what the AF solution would have been, had it been run at the temperature and altitude of AF Run 1 on Lum. @@ -1726,7 +1726,7 @@ - If you hover the mouse over an AF Run it will show a tooltip Adaptive Focus Explainer. In the example, the mouse if hovering over + If you hover the mouse over an AF Run it will show a tooltip Adaptive Focus Explainer. In the example, the mouse is hovering over AF Run 1 on Red. The 1st row of the Explainer shows the measured Autofocus result for that run (36683), adaptations for Temperature (0.0C) and Altitude (0.2 degrees Alt). The 2nd row of the Explainer shows the Adaptations: 206 total, 0 temperature, 205.9 altitude. The 3rd row shows the Adapted Position of 36889. @@ -2190,7 +2190,7 @@ starting at 36580, before moving to 36571 and then to 36562 as shown on the Focus Tab in the Current Position widget and in the message box. - The Adaptive Focus concept has been build into the Build Offsets tool. + The Adaptive Focus concept has been built into the Build Offsets tool.
[education/kstars] doc: Fix minor typos
Git commit 8c97889c0accfc3a3e2b3aa1997448206c900c39 by Yuri Chornoivan. Committed on 06/07/2023 at 12:10. Pushed by yurchor into branch 'master'. Fix minor typos M +2-2doc/ekos-focus.docbook https://invent.kde.org/education/kstars/-/commit/8c97889c0accfc3a3e2b3aa1997448206c900c39 diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook index f2b7bb710..6932da769 100644 --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -2027,14 +2027,14 @@ Temperature. All the components of the imaging system will be affected by changes in ambient temperature. The most obvious will be the telescope tube. Typically this will expand as temperature increases and contract as -it descreases. This will affect the focus point. But also the optical path the light from the imaged target takes +it decreases. This will affect the focus point. But also the optical path the light from the imaged target takes through the atmosphere and through the imaging components of the telescope will be affected by temperature and therefore will affect the focus point. It is necessary to have a reliable source of temperature information available to the focus module in order to use the temperature feature of AF. - Where the temperature source is located is, of course, upto the user. Given the changes in temperature effect + Where the temperature source is located is, of course, up to the user. Given the changes in temperature effect many components it is not obvious where the best location would be. Some experimentation may be required to get the best results but as a guide, the source should be near the imaging train but not near any heating effect of electrical equipment that would say, heat the temperature source but not the optical train. Consistency of location
[education/kstars] doc: Fix minor typos
Git commit 3525b0b4e10937840f5933437a7a8f46e0c39cb9 by Yuri Chornoivan. Committed on 05/07/2023 at 15:00. Pushed by yurchor into branch 'master'. Fix minor typos M +9-9doc/ekos-scheduler.docbook https://invent.kde.org/education/kstars/-/commit/3525b0b4e10937840f5933437a7a8f46e0c39cb9 diff --git a/doc/ekos-scheduler.docbook b/doc/ekos-scheduler.docbook index 7a67d5772..aba7d853c 100644 --- a/doc/ekos-scheduler.docbook +++ b/doc/ekos-scheduler.docbook @@ -21,13 +21,13 @@ Introduction - The Ekos Scheduler is an important component of you imaging workflow. It connects to INDI, starts and stops all the other Ekos modules, schedules jobs according to their constraints and priorities, monitors those jobs as they execute, and then safely brings down the system when jobs are done, or before dawn. Whether you are running multi-day imaging sessions for multiple targets, or simplying trying to image a single target for a few hours, it is advisable to have the Scheduler control your imaging sessions. + The Ekos Scheduler is an important component of your imaging workflow. It connects to INDI, starts and stops all the other Ekos modules, schedules jobs according to their constraints and priorities, monitors those jobs as they execute, and then safely brings down the system when jobs are done, or before dawn. Whether you are running multi-day imaging sessions for multiple targets, or simply trying to image a single target for a few hours, it is advisable to have the Scheduler control your imaging sessions. Scheduler Table - The heart of the Scheduler is a table displaying the list of Scheduler jobs the user wants to run. Associated with each jobs are attributes (mostly described in the settings section below). The attributes describe the name of the job, where the telescope should be pointed when imaging that job, a description of what types of images should be captured, constraints about when the jobs should run (e.g. altitude, twilight, moon, landscape blockages, etc), things that need to be done before and after the job is run, and strategies for dealing with errors. + The heart of the Scheduler is a table displaying the list of Scheduler jobs the user wants to run. Associated with each jobs are attributes (mostly described in the settings section below). The attributes describe the name of the job, where the telescope should be pointed when imaging that job, a description of what types of images should be captured, constraints about when the jobs should run ( altitude, twilight, moon, landscape blockages, ), things that need to be done before and after the job is run, and strategies for dealing with errors. You can add, delete, modify or change the order of rows in the Scheduler table. @@ -64,16 +64,16 @@ The Scheduler table (above) lists jobs in order of priority, with higher jobs (on lower-numbered rows) having higher priority than jobs further down the list (with higher-numbered rows). - The Scheduler regularly plans (an re-plans) which jobs should be run, and when. It can start executing a given job, and then later preempt that job for a new one. It can become idle if no jobs can be run (e.g. in daylight), and sleep until such a time that it becomes active again. Its aim is to keep the equipment as busy as possible, while respecting the scheduler-table's priorities. Here's how it works. + The Scheduler regularly plans (and re-plans) which jobs should be run, and when. It can start executing a given job, and then later preempt that job for a new one. It can become idle if no jobs can be run ( in daylight), and sleep until such a time that it becomes active again. Its aim is to keep the equipment as busy as possible, while respecting the scheduler-table's priorities. Here's how it works. - When the scheduler starts (or when it replans, which it does every second while active), it looks through the entire list of jobs, starting at the highest priority job, and working its way down to the lowest priority one if necessary. When it finds a job that can run, it starts that job, possibly preempting the currently running job. A jobs can run if it's constraints are met, e.g. the target is not blocked by the local terrain, it meets the minimum altitude constraint, it has not already completed all the desired imaging, ... + When the scheduler starts (or when it replans, which it does every second while active), it looks through the entire list of jobs, starting at the highest priority job, and working its way down to the lowest priority one if necessary. When it finds a job that can run, it starts that job, possibly preempting the currently running job. A jobs can run if its constraints are met, the target is not blocked by the local terrain, it
[education/kstars] doc: Fix minor typos
Git commit ccbee55ba492ae5ed09958258553272f6f373207 by Yuri Chornoivan. Committed on 04/07/2023 at 03:46. Pushed by yurchor into branch 'master'. Fix minor typos M +2-2doc/ekos-scheduler.docbook https://invent.kde.org/education/kstars/-/commit/ccbee55ba492ae5ed09958258553272f6f373207 diff --git a/doc/ekos-scheduler.docbook b/doc/ekos-scheduler.docbook index d07135377..7a67d5772 100644 --- a/doc/ekos-scheduler.docbook +++ b/doc/ekos-scheduler.docbook @@ -58,13 +58,13 @@ - + Scheduling Algorithm The Scheduler table (above) lists jobs in order of priority, with higher jobs (on lower-numbered rows) having higher priority than jobs further down the list (with higher-numbered rows). - The Scheduler regularly plans (an re-plans) which jobs should be run, and when. It can start executing a given job, and then later preempt that job for a new one. It can become idle if no jobs can be run (e.g. in daylight), and sleep until such a time that it becomes active again. Its aim is to keep the equipment as busy as possible, while respecting the scheduler-table's priorties. Here's how it works. + The Scheduler regularly plans (an re-plans) which jobs should be run, and when. It can start executing a given job, and then later preempt that job for a new one. It can become idle if no jobs can be run (e.g. in daylight), and sleep until such a time that it becomes active again. Its aim is to keep the equipment as busy as possible, while respecting the scheduler-table's priorities. Here's how it works. When the scheduler starts (or when it replans, which it does every second while active), it looks through the entire list of jobs, starting at the highest priority job, and working its way down to the lowest priority one if necessary. When it finds a job that can run, it starts that job, possibly preempting the currently running job. A jobs can run if it's constraints are met, e.g. the target is not blocked by the local terrain, it meets the minimum altitude constraint, it has not already completed all the desired imaging, ...
[education/kstars] doc: Fix minor typos
Git commit 94c81b8120f4912f087936b0f488183b072edafa by Yuri Chornoivan. Committed on 30/06/2023 at 19:14. Pushed by yurchor into branch 'master'. Fix minor typos M +2-2doc/ekos-focus.docbook https://invent.kde.org/education/kstars/-/commit/94c81b8120f4912f087936b0f488183b072edafa diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook index 84b82195e3..f2b7bb7106 100644 --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -1029,7 +1029,7 @@ applicable here as well. The difference between CFZ Shuffle and Fixed Steps is that near the center of the sweep (which -should be around the Critical Focus Zone (CFZ) the algorithm takes steps of half the specified size. +should be around the Critical Focus Zone (CFZ)) the algorithm takes steps of half the specified size. @@ -1255,7 +1255,7 @@ have how many ticks moved the drawtube the distance you measured. From this you can calculate the distance in microns a single tick moves the drawtube. Other types of telescope will have other ways to adjust the focal plane, for example, by moving the primary or -secondary mirrors. You will need to either get the Step Size from the documentation for your equipment of work out how to +secondary mirrors. You will need to either get the Step Size from the documentation for your equipment or work out how to measure it in a way that are consistent with that described above.
[education/kstars] doc: Fix minor typos
Git commit 99158d07034dcf2aa00d8311eed15696140c21e6 by Yuri Chornoivan. Committed on 22/06/2023 at 12:52. Pushed by yurchor into branch 'master'. Fix minor typos M +7-7doc/ekos-focus.docbook https://invent.kde.org/education/kstars/-/commit/99158d07034dcf2aa00d8311eed15696140c21e6 diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook index 153ec23bc..50d31cee0 100644 --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -832,7 +832,7 @@ - # Stars: This ia an experimental feature that + # Stars: This is an experimental feature that calculates the number of stars in the image and uses this number as the focus measure. The idea is that as you move nearer focus so more stars become detectable. @@ -900,7 +900,7 @@ 1 Pass focus algorithm and Curve Fits of Hyperbola and Parabola. If this option is checked then at the end of the sweep of datapoints, Ekos fits a curve and measures the R². It then applies Peirce's Criterion based on Gould's methodology for outlier identification. See https://en.wikipedia.org/wiki/Peirce%27s_criterion;>Peirce's Criterian for details incl + url="https://en.wikipedia.org/wiki/Peirce%27s_criterion;>Peirce's Criterion for details incl Peirce's original paper and Gould's paper which are both referenced in the notes. If Peirce's Criterion detects 1 or more outliers then another curve fit is attempted with the outliers removed. Again the R² is calculated and compared with the original curve fit R². If the R² is better, then the latest run is used, @@ -1196,7 +1196,7 @@ - Tolerance: This is used by Classic and Wavwfront algorithms and is a scaling factor + Tolerance: This is used by Classic and Wavefront algorithms and is a scaling factor between 0 and 1. For the Classic algorithm, Goldman and Megdal suggest 1/3. For the Wavefront algorithm, some have suggested 1/3 or even 1/10. @@ -1402,11 +1402,11 @@ Use Offsets: It is possible to use filter offsets to adjust focus when swapping between filters, without running Autofocus. This requires some setup work ahead of time but has the advantage of - reduciung the number of Autofocus runs and therefore reducing the time spent autofocusing. + reducing the number of Autofocus runs and therefore reducing the time spent autofocusing. In order to use this feature it is necessary to work out the relative focus position between all filters that you wish to use this functionality for. For example, if Lum and Red have the same focus position (they are parfocal) but Green - focuses 300 ticks further out than Lum (or Red) then setup Offsets for Lum, Red and Grren as 0, 0, 300 as shown above. If a + focuses 300 ticks further out than Lum (or Red) then setup Offsets for Lum, Red and Green as 0, 0, 300 as shown above. If a sequence is created to take 10 subframes of Lum, then 10 Red, then 10 Green, then at the start, since Lum has Auto Focus checked, an Autofocus will be run on Lum and the 10 subs taken. Capture will then switch filters to Red. Since Red has Auto Focus unchecked no Autofocus will happen and Ekos will look to the @@ -1774,7 +1774,7 @@ The units of the y-axis depend on the selected focus Measure. For example, for HFR, the y-axis will either be in Pixels or Arc seconds depending on how Display Units is set. - If Refine Curve Fit is selected, Focus will check for and potentially exclude outlying datapoonts. + If Refine Curve Fit is selected, Focus will check for and potentially exclude outlying datapoints. In this case datapoints 1, 5 and 7 were excluded. Under the V-Curve a number of parameters are displayed: @@ -1825,7 +1825,7 @@ Here is a V-Curve when Measure is set to Fourier: V-Curve Fourier - Focus V-Curve Fourierj + Focus V-Curve Fourier When Framing, the graph format changes to that of a "time series" where horizontal axis denotes the frame number. This is to aid you in the framing process as you can see how Measure, in this case HFR, changes between frames.
[education/kstars] doc: Fix minor typos
Git commit a32a545422bd1eac0b4f6ca655d1f2363f85e807 by Yuri Chornoivan. Committed on 20/06/2023 at 12:47. Pushed by yurchor into branch 'master'. Fix minor typos M +9-9doc/ekos-focus.docbook https://invent.kde.org/education/kstars/-/commit/a32a545422bd1eac0b4f6ca655d1f2363f85e807 diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook old mode 100755 new mode 100644 index 51253ca27..153ec23bc --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -53,7 +53,7 @@ is recommended to allow Ekos to select a set of stars. Ekos supports 4 different focus algorithms: Linear 1 Pass, Linear, -Iterative, Polynominal. Linear 1 Pass is the recommended algorithm. +Iterative, Polynomial. Linear 1 Pass is the recommended algorithm. @@ -560,7 +560,7 @@ Correcting image tilt: especially large sensors are very sensitive to incorrect distance and tilting of the sensor. In such cases, the image - shows aberration, expecially in the image corners. If all corners show the same + shows aberration, especially in the image corners. If all corners show the same effect, the distance needs to be corrected. If the aberrations in the corners differ, this is typically the result of a tilted sensor. @@ -863,7 +863,7 @@ PSF: If Measure is set to FWHM, then the PSF - widget can be selected for use in fitting a surface to the star. At pressent just Gaussian is + widget can be selected for use in fitting a surface to the star. At present just Gaussian is supported. @@ -1248,7 +1248,7 @@ Step Size: This must be input by the user (as it cannot be calculated by Ekos). It relates how far 1 tick moves the focal plane in microns. For a refractor this is how far the drawtube moves when the focuser is moved by 1 tick. You might be able to get this -value from the spefication of your focuser (how many ticks for a complete revolution of your focuser) and the thread pitch of +value from the specification of your focuser (how many ticks for a complete revolution of your focuser) and the thread pitch of your telescope drawtube along with any gearing involved. Alternatively, you can measure how far the drawtube moves from end to end (be careful not to force the drawtube) with a set of calipers or a ruler. By subtracting the furthest "in" position (in ticks) from the furthest "out" position (in ticks) you @@ -1405,12 +1405,12 @@ reduciung the number of Autofocus runs and therefore reducing the time spent autofocusing. In order to use this feature it is necessary to work out the relative focus position between all filters that you - wish to use this functionality for. For examplke, if Lum and Red have the same focus position (they are parfocal) but Green + wish to use this functionality for. For example, if Lum and Red have the same focus position (they are parfocal) but Green focuses 300 ticks further out than Lum (or Red) then setup Offsets for Lum, Red and Grren as 0, 0, 300 as shown above. If a sequence is created to take 10 subframes of Lum, then 10 Red, then 10 Green, then at the start, since Lum has Auto Focus checked, an Autofocus will be run on Lum and the 10 subs taken. Capture will then switch filters to Red. Since Red has Auto Focus unchecked no Autofocus will happen and Ekos will look to the - Offsets between Red and Lum. In this case 0 - 0 = 0. So the focuser will not be moved and Copture will take 10 subs of Red. + Offsets between Red and Lum. In this case 0 - 0 = 0. So the focuser will not be moved and Capture will take 10 subs of Red. Then Capture will swap from Red to Green. Again, Green has Auto Focus unchecked no Autofocus will happen and Ekos will look to the Offsets between Green and Red. In this case 300 - 0 = 300. So Focus will adjust the focus position by +300 (move the focuser out by 300 ticks). Capture will then take the 10 Green subs. @@ -1772,7 +1772,7 @@ is selected then error bars are indicated on each datapoint that correspond to the standard deviation in measured value. The units of the y-axis depend on the selected focus Measure. For example, for HFR, the y-axis will either be in Pixels -or Arc Sseconds depending on how Display Units is set. +or Arc seconds depending on how Display Units is set. If Refine Curve Fit is selected, Focus will check for and potentially exclude outlying datapoonts. In this case datapoints 1, 5 and 7 were excluded. @@ -2067,7 +2067,7 @@ Currently Ekos supports a simple linear relationship between temperature, or altitude, and ticks. In the future, if there is demand, more
[education/kstars] doc: Fix minor typos
Git commit 8294000cc8d6ae94e3c5ce2f4b9d01000581c194 by Yuri Chornoivan. Committed on 16/01/2023 at 11:28. Pushed by yurchor into branch 'master'. Fix minor typos M +5-5doc/ekos-align.docbook https://invent.kde.org/education/kstars/commit/8294000cc8d6ae94e3c5ce2f4b9d01000581c194 diff --git a/doc/ekos-align.docbook b/doc/ekos-align.docbook index 94a506d0d..f2941416b 100644 --- a/doc/ekos-align.docbook +++ b/doc/ekos-align.docbook @@ -554,7 +554,7 @@ However, unless you have a top of the line mount, then you'd probably want to use an autoguider to keep the same star locked in the same position over time. Despite all of this, if the axis of the mount is not properly aligned with the celestial pole, then even a mechanically-perfect mount would lose tracking with time. Tracking errors are proportional to the magnitude of the misalignment. It is therefore very important for long exposure imaging to get the mount polar aligned to reduce any residual errors as it spans across the sky. -Before starting the process, point the mount as close as possible to the celestial pole with the counterweights down. If you are living in the Northern Hemisphere, point it as close as possible to Polaris. If Polaris is not visible (e.g. blocked by trees or buildings) you may point elsewhere, preferably near the Meridian. Make sure there is at 30-60 degrees of sky viewable in an arc East or West of the Meridian from the position you choose. Select the direction of free sky, the number of degrees for each of two slews, the mount slew speed, and whether the mount will be slewing automatically (recommended) or manually. +Before starting the process, point the mount as close as possible to the celestial pole with the counterweights down. If you are living in the Northern Hemisphere, point it as close as possible to Polaris. If Polaris is not visible ( blocked by trees or buildings) you may point elsewhere, preferably near the Meridian. Make sure there is at least 30-60 degrees of sky viewable in an arc East or West of the Meridian from the position you choose. Select the direction of free sky, the number of degrees for each of two slews, the mount slew speed, and whether the mount will be slewing automatically (recommended) or manually. The tool works by capturing and solving three images. After capturing each, the mount rotates by the fixed amount you entered and another image is captured and solved. If you chose manual, you will need to slew the mount by roughly the angle chosen. @@ -593,13 +593,13 @@ - If your error is low enough (e.g. less than an arc-minute) then you don't need to make any adjustments. Simply press stop and you're done. + If your error is low enough ( less than an arc-minute) then you don't need to make any adjustments. Simply press stop and you're done. - If you will be making corrections to your mount's axis, you should select the adjustment approach (we're using Plate Solve in this example), and how often the system should recapture images to re-measure the polar alignment error. The refresh interval should be frequent, but it doesn't make sense to make it faster that your CPU can capture and plate-solve the images. We're using 2s in this example. Then press the Refresh button to begin the correction process. + If you will be making corrections to your mount's axis, you should select the adjustment approach (we're using Plate Solve in this example), and how often the system should recapture images to re-measure the polar alignment error. The refresh interval should be frequent, but it doesn't make sense to make it faster that your CPU can capture and plate-solve the images. We're using 2s in this example. Then press the Refresh button to begin the correction process. - The system will capture images, and re-estimate the polar alignment error after each image. You can try to reduce the error by adjusting the Alititude and Azimuth correction knobs on your mount. The image below shows the screen after the altitude error has been almost zeroed. See the difference between the Measured Error row, which shows the originally measured error after the original 3 captures, and the Updated Error row which shows the current error estimate. + The system will capture images, and re-estimate the polar alignment error after each image. You can try to reduce the error by adjusting the Altitude and Azimuth correction knobs on your mount. The image below shows the screen after the altitude error has been almost zeroed. See the difference between the Measured Error row, which shows the
[education/kstars] doc: Fix minor typos
Git commit ab1918351666930fc19cfd091a76ddee4eb7df98 by Yuri Chornoivan. Committed on 21/10/2022 at 14:29. Pushed by yurchor into branch 'master'. Fix minor typos M +2-2doc/ekos-focus.docbook https://invent.kde.org/education/kstars/commit/ab1918351666930fc19cfd091a76ddee4eb7df98 diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook index 0aebc2836..15be57eb4 100644 --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -523,7 +523,7 @@ Backlash Managed by Focuser: If your focuser had the ability to manage backlash itself then you can use this facility and turn off AF - Backlash Comp. Alternatively, if its possible, you could turn + Backlash Comp. Alternatively, if it's possible, you could turn off the focuser's backlash facility and set AF Backlash Comp on. @@ -532,7 +532,7 @@ Backlash Managed by Device Driver: If your device driver had the ability to manage backlash itself then you can use this facility and turn - off AF Backlash Como. Alternatively, if its possible, you could + off AF Backlash Comp. Alternatively, if it's possible, you could turn off the device driver's backlash facility and set AF Backlash Comp on.
[education/kstars] doc: Fix minor typos
Git commit 812db50416488f97c55dd6eb548b1fde78f8fa9b by Yuri Chornoivan. Committed on 28/07/2022 at 06:48. Pushed by yurchor into branch 'master'. Fix minor typos M +2-2doc/ekos-profile-editor.docbook https://invent.kde.org/education/kstars/commit/812db50416488f97c55dd6eb548b1fde78f8fa9b diff --git a/doc/ekos-profile-editor.docbook b/doc/ekos-profile-editor.docbook index 070fca1da..abc455b2f 100644 --- a/doc/ekos-profile-editor.docbook +++ b/doc/ekos-profile-editor.docbook @@ -38,7 +38,7 @@ -Port Selector: Check this option to enable Port Selector. When creating a new profile, it is checked by default. Port Selector is used to select initial serial and network communication parameters for the devices in the equipment profile. After connecting to equipment for the first time, the Port Selector popup is displayed where the communication parameters can be set before establishing connection. Once connected, the Port Selector option is turned off. it can be toggled to checked in the profile editor to enable it back. +Port Selector: Check this option to enable Port Selector. When creating a new profile, it is checked by default. Port Selector is used to select initial serial and network communication parameters for the devices in the equipment profile. After connecting to equipment for the first time, the Port Selector popup is displayed where the communication parameters can be set before establishing connection. Once connected, the Port Selector option is turned off. It can be toggled to checked in the profile editor to enable it back. @@ -63,7 +63,7 @@ -Scripts: Adjust pre-driver and post-driver delays and scripts for each driver. A rule can be defined for each driver in case there is a need to introduce delays before and/or after starting a particular driver. The fields before the driver selection dropdown are to be executed before the driver is started, whereas the fields after the driver selection dropdown are to be executed after the driver started. The script field, if specified, should include the full path to an executable script with the appropiate permissions. All drivers configured in the scripts editor would be started first and in order before the rest of the equipment profile drivers. +Scripts: Adjust pre-driver and post-driver delays and scripts for each driver. A rule can be defined for each driver in case there is a need to introduce delays before and/or after starting a particular driver. The fields before the driver selection dropdown are to be executed before the driver is started, whereas the fields after the driver selection dropdown are to be executed after the driver started. The script field, if specified, should include the full path to an executable script with the appropriate permissions. All drivers configured in the scripts editor would be started first and in order before the rest of the equipment profile drivers.
[education/kstars] doc: Fix minor typos
Git commit 922b8d538bfaa2dc2d3ffe4b715e51dff48933d6 by Yuri Chornoivan. Committed on 25/07/2022 at 17:47. Pushed by yurchor into branch 'master'. Fix minor typos M +3-3doc/ekos-focus.docbook https://invent.kde.org/education/kstars/commit/922b8d538bfaa2dc2d3ffe4b715e51dff48933d6 diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook index a93ed92ba..96c76b29e 100644 --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -1122,7 +1122,7 @@ - In contract, the next picture shows an Initial Step Size + In contrast, the next picture shows an Initial Step Size that has been set too low. The HFR varies from about 0.78 to 0.72. Which gives a max / min just over 1. The other clue that this is a poor setup is that the Error Bar range is very large compared to @@ -1165,7 +1165,7 @@ obtain, but as a guide, a value above, say 0.8 would be a good fit. There is an option to set an “R² Limit” in the Settings tab of the -Focus window that is compared to the calculated R² after the auto focu run +Focus window that is compared to the calculated R² after the auto focus run has completed. If the limit value has not been achieved, then the auto focus is rerun. @@ -1210,7 +1210,7 @@ curve fits the data as best as it can. P is a set of parameters that are varied by the solver in order to find the best fit. The solver measures how far away the curve is at each data point, squares the result and adds -them all up. This is the number to be minimized, lets call is S. The +them all up. This is the number to be minimized, let's call it S. The solver is supplied with an initial guess for the parameters, P. It calculates S, makes an adjustment to P and calculates a new S1. Provided S1 S then we are moving in the right direction. It iterates through
[education/kstars] doc: Fix minor typos
Git commit 07264068791588510022f73a2e3b2b437d799367 by Yuri Chornoivan. Committed on 22/07/2022 at 06:22. Pushed by yurchor into branch 'master'. Fix minor typos M +6-6doc/ekos-focus.docbook https://invent.kde.org/education/kstars/commit/07264068791588510022f73a2e3b2b437d799367 diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook index b2c9fc51f..b2ab39a1d 100644 --- a/doc/ekos-focus.docbook +++ b/doc/ekos-focus.docbook @@ -91,7 +91,7 @@ The algorithm works on a "good enough" paradigm whereby it -stops when the HFR is within % Tolerance of the perceived mimimum. +stops when the HFR is within % Tolerance of the perceived minimum. @@ -275,7 +275,7 @@ it is best to start from a position of being approximately in focus. For first time setup, Start Framing can be used along with the In and Out buttons -to adjust the focus position to roughly minimise the HFR of the stars in +to adjust the focus position to roughly minimize the HFR of the stars in the captured images. When Framing is used in this way, the V-Curve graph changes to show a time series of frames and their associated HFRs. This makes the framing process much @@ -666,7 +666,7 @@ - Kernal Size: The kernal size of the + Kernel Size: The kernel size of the gaussian blur applied to the image before applying Bahtinov edge detection. Used when Detection is Bahtinov. @@ -1071,7 +1071,7 @@ Setup Backlash. See the Backlash section for more details -but if you don’tknow the value for your equipment then set to +but if you do not know the value for your equipment then set to 0. @@ -1202,7 +1202,7 @@ - The Levenberg-Marquart algorithm is a new feature added for the + The Levenberg-Marquardt algorithm is a new feature added for the Linear 1 Pass focus algorithm. It is a non-linear least-squares solver and thus suitable for many different equations. The basic idea is to adjust the equation y = f(x,P) so that the computed y values are as close as @@ -1210,7 +1210,7 @@ curve fits the data as best as it can. P is a set of parameters that are varied by the solver in order to find the best fit. The solver measures how far away the curve is at each data point, squares the result and adds -them all up. This is the number to be minimised, lets call is S. The +them all up. This is the number to be minimized, lets call is S. The solver is supplied with an initial guess for the parameters, P. It calculates S, makes an adjustment to P and calculates a new S1. Provided S1 S then we are moving in the right direction. It iterates through
[education/kstars] doc: Fix minor typos
Git commit dbb44aca4144500c759676a739455f768184a7db by Yuri Chornoivan. Committed on 04/01/2022 at 15:17. Pushed by yurchor into branch 'master'. Fix minor typos M +3-3doc/ekos-scheduler.docbook https://invent.kde.org/education/kstars/commit/dbb44aca4144500c759676a739455f768184a7db diff --git a/doc/ekos-scheduler.docbook b/doc/ekos-scheduler.docbook index 84da8fa65..dde3555e2 100644 --- a/doc/ekos-scheduler.docbook +++ b/doc/ekos-scheduler.docbook @@ -329,7 +329,7 @@ exit(0) The 2nd step is handled by image processing applications such as https://pixinsight.com;>PixInsight, among others, and will not be the topic of discussion here. The first step can be accomplished in Ekos Scheduler where it creates a mosaic suitable for your equipment and in accordance with the desired field of view. Not only Ekos creates the mosaic panels for your target, but it also constructs the corresponding observatory jobs required to capture all the images. This greatly facilitates the logistics of capturing many images with different filters and calibration frames across a wide area of the sky. -The Mosaic Job Creator in the Ekos Scheduler will create multiple Scheduler jobs based on a central target. It requires that you select first one target and one sequence file. The Sequence File contains all the information necessary to capture an image including exposure time, filters, temperature setting, etc, and that information will be used for each pane of the mosaic. Observation job conditions and constraints shall be assigned too, so check that they are as per your requirements. You may simply prepare a new job without adding it, or pick an existing job, as long as both target and sequence file fields are valid in the Scheduler form. If you added jobs to the observation list previously, Ekos will ask you if you would want to keep or remove them before inserting the mosaic jobs in the list. +The Mosaic Job Creator in the Ekos Scheduler will create multiple Scheduler jobs based on a central target. It requires that you select first one target and one sequence file. The Sequence File contains all the information necessary to capture an image including exposure time, filters, temperature setting, , and that information will be used for each pane of the mosaic. Observation job conditions and constraints shall be assigned too, so check that they are as per your requirements. You may simply prepare a new job without adding it, or pick an existing job, as long as both target and sequence file fields are valid in the Scheduler form. If you added jobs to the observation list previously, Ekos will ask you if you would want to keep or remove them before inserting the mosaic jobs in the list. When your target and conditions are ready, start the Mosaic Job Creator by clicking on the icon next to the Find button in Ekos Module. A new window will open with a left-side form and your target centered in a sky chart. For convenience, maximize that window. There is a help icon on the top left part of the sky chart. Move your mouse over it to display the latest documentation of the tool. Each gadget also has its own tooltip. @@ -367,7 +367,7 @@ exit(0) -A large overlap will make frame stitching easier during post-processing, but it requires more panes to cover the desired extent. However, if you already know the minimal amount of sub-frames your rejection algorithm will use during post-processing, you may want to increase the overlap to attain that amount on the areas covered by multiple panes. For instance, a 4x4 mosaic grid with 75% overlap has 16 sub-frames covering the central intersection, which is enough for Windsorized Sigma rejection. Although the resulting stack does not have the same height on all parts of the final frame, this method gives you control on signal-to-noise ratio and allows you to provide context to your target while exposing a relatively low number of captures. +A large overlap will make frame stitching easier during post-processing, but it requires more panes to cover the desired extent. However, if you already know the minimal amount of sub-frames your rejection algorithm will use during post-processing, you may want to increase the overlap to attain that amount on the areas covered by multiple panes. For instance, a 4x4 mosaic grid with 75% overlap has 16 sub-frames covering the central intersection, which is enough for Winsorized Sigma rejection. Although the resulting stack does not have the same height on all parts of the final frame, this method gives you control on signal-to-noise ratio and allows you to provide context to your target while exposing a relatively low number of captures. @@ -399,7 +399,7 @@ exit(0) -If you need to
[education/kstars] doc: Fix minor typos
Git commit 6123fa93ede1336fd8ade93502f93577b72721ea by Yuri Chornoivan. Committed on 22/07/2021 at 06:53. Pushed by yurchor into branch 'master'. Fix minor typos M +1-1doc/calc-sidereal.docbook M +1-1doc/commands.docbook https://invent.kde.org/education/kstars/commit/6123fa93ede1336fd8ade93502f93577b72721ea diff --git a/doc/calc-sidereal.docbook b/doc/calc-sidereal.docbook index 757873c9c..a68225af7 100644 --- a/doc/calc-sidereal.docbook +++ b/doc/calc-sidereal.docbook @@ -31,7 +31,7 @@ There is a batch mode for this module. To use it, simply generate an input file whose lines each contain values for the input parameter: sidereal time or standard time. You can choose to set the Date: and Location: in the -current window, or you can tell to read this values from the Input file:. +current window, or you can tell to read these values from the Input file:. Then specify the input and output filenames, and press the Compute button to generate the output file. The output file will contains values for the complementary parameter. For example, diff --git a/doc/commands.docbook b/doc/commands.docbook index de22490d2..edd3ac551 100644 --- a/doc/commands.docbook +++ b/doc/commands.docbook @@ -397,7 +397,7 @@ which provides full access to many of the mathematical functions used by View Devices -A submenu for control suported devices. +A submenu for control supported devices.
[education/kstars] doc: Fix minor typos
Git commit 45c9695b8d3a4e86345ed7139ba4d4e9c26afedb by Yuri Chornoivan. Committed on 14/07/2021 at 12:36. Pushed by yurchor into branch 'master'. Fix minor typos M +2-2doc/config.docbook https://invent.kde.org/education/kstars/commit/45c9695b8d3a4e86345ed7139ba4d4e9c26afedb diff --git a/doc/config.docbook b/doc/config.docbook index 3277a12dd..040608109 100644 --- a/doc/config.docbook +++ b/doc/config.docbook @@ -966,14 +966,14 @@ selected object. -In the top right you can choose whether coordinated are being +In the top right you can choose whether coordinates are being expressed in degrees or hours/minutes/seconds. The Mapping section lets you map columns in the CSV file to data fields in . Selecting Ignore assigns the default value for this field. Entering your own text will use this as the value for every object being read. The Type -Mapping sections maps strings to object types. You can add +Mapping section maps strings to object types. You can add and remove mappings by clicking + or -. When you're done mapping, you can test your settings by clicking Preview to read the
[education/kstars] doc: Fix minor typos in docs
Git commit 8919454bebb44cc546b476fc5656be26b6a3807b by Yuri Chornoivan. Committed on 18/06/2021 at 08:11. Pushed by yurchor into branch 'master'. Fix minor typos in docs M +11 -11 doc/config.docbook https://invent.kde.org/education/kstars/commit/8919454bebb44cc546b476fc5656be26b6a3807b diff --git a/doc/config.docbook b/doc/config.docbook index fc5e007f2..85dfcb1bd 100644 --- a/doc/config.docbook +++ b/doc/config.docbook @@ -454,16 +454,16 @@ the list of deep-sky objects includes the Messier, NGC and IC catalogs. Addons catalogs are available via the DataDownload New Data... submenu where you can download -catalogs provided by team and the community though +catalogs provided by team and the community through the https://invent.kde.org/vboettcher/kstars-catalogs;>catalog packaging repository. The DSO Minimal -Zoom slider controls the minimal zoomlevel for which the +Zoom slider controls the minimal zoom level for which the DSOs are shown. Increasing the minimal zoom level can lead to performance improvements when panning the skymap zoomed-out. The DSO Cache Percentage slider regulates how much of the DSO master catalog is being kept in memory. If you -experience memory issues with large catalogs, try lowering -percentage. The Label density slider controlls +experience memory issues with large catalogs, try lowering the +percentage. The Label density slider controls the perceived density of labels for the DSOs. If labels start to overlap and the skymap begins to look too crowded, try tuning this option. The Faint limit regulates up to which @@ -494,14 +494,14 @@ the future. DSO catalogs in are just SQL (sqlite3) database tables. Each catalog is represented by its own table which contains all its objects -and an entry in a catalog meta-data table. Additionally catalogs may be -imported or exported from and into stand-alone database files. +and an entry in a catalog meta-data table. Additionally, catalogs may be +imported or exported from and into stand-alone database files. -Each object has the usual properties like name and coordinates, but +Each object has the usual properties like name and coordinates but additionally features two IDs. The first ID is the unique identifier -for the specific object and calculated by hashing all the object fields +for the specific object and is calculated by hashing all the object fields along with the catalog id. Because objects can be contained in several catalogs each object has an additional object id (OID) that identifies the physical object and may be shared by several objects of different @@ -510,7 +510,7 @@ catalogs. To speed up object lookup all enabled catalogs are merged into a -master table. Each catalog has a priority number and if several +master table. Each catalog has a priority number and if several objects with the same OID occur the one from the catalog with the highest priority is loaded. The objects from the master catalog are then drawn on the sky and generally available in . @@ -525,9 +525,9 @@ reproducibly build catalogs in a homogeneous environment. Every catalog is implemented https://invent.kde.org/vboettcher/kstars-catalogs/-/blob/master/catalogs/sharpless_2.py;> as a python module and provides standard methods to acquire -data, parse it and to find duplicates in other catalogs. All +data, parse it and find duplicates in other catalogs. All downloadable catalogs are implemented this way. If you'd like to make -a catalog of you own available for , it is recommended that you +a catalog of your own available for , it is recommended that you implement it as a package in the repository. The tooling provided there is so flexible, that it should work for you. For more information on how to do that see
