התחל

Astrology

blueprint_ephemeris_lib🔭 Library blueprint_ephemeris_lib Consolidated planetary ephemeris library with improved accuracy. Supersedes previous individual planet libraries (lib_vsop_core, lib_vsop_mercury, lib_vsop_venus, etc.). One import gives you geocentric/heliocentric positions for all 10 solar system bodies. █ ACCURACY — VALIDATED AGAINST JPL DE440 Every planetary body was validated against NASA's DE440 ephemeris (via Skyfield). Using only 1.6% of the full VSOP87D theory (511 of 31,577 terms), this library achieves sub-arcminute accuracy for all planets: Sun 0.004° (14 arcseconds) Mercury 0.005° (18") Venus 0.006° (22") Mars 0.010° (36") Jupiter 0.007° (25") Saturn 0.009° (32") Uranus 0.013° (47") Neptune 0.017° (61") Moon 0.062° (3.7') Pluto 0.059° (3.5') All bodies under 0.1° RMS — more than sufficient for aspect calculations, ingress timing, and planetary line work. The Sun is accurate to 14 arcseconds using a truncated series that fits entirely inside Pine Script's token limits. █ WHAT'S NEW (V2) The original ephemeris required 11 chained library imports. A full validation audit uncovered critical coefficient errors and motivated this rewrite: • L1 Precession Fix — All 8 VSOP87 planets had incorrect longitude rate coefficients (VSOP87B values instead of VSOP87D). Each was missing +0.24382 rad/millennium of general precession. This single correction reduced error from ~0.75° to < 0.1° across the board. • 28% Smaller — 4,300 lines across 11 files → ~3,100 lines in 1 file. • Single Import — No dependency chain. Faster execution. • Moon Improvements — Functions accept raw `time` directly. Node functions renamed with explicit north/south designation. █ THEORIES VSOP87D (Bretagnon & Francou, 1988) — Mercury through Neptune 511 truncated terms out of 31,577 total (1.6%). Heliocentric spherical coordinates in the ecliptic of date. ELP2000-82 (Chapront-Touzé & Chapront, 1983) — Moon 91 terms (48 longitude + 43 latitude) from Meeus Chapter 47. Meeus Series (Meeus, 1998) — Pluto Analytical series from "Astronomical Algorithms" Ch. 37. Valid ±1 century from J2000. █ HOW TO USE Import the library: import BlueprintResearch/blueprint_ephemeris_lib/1 as eph Basic — plot a planet's geocentric longitude and declination: float jupiter_lon = eph.get_longitude(eph.Planet.Jupiter, time, true) float jupiter_decl = eph.get_declination(eph.Planet.Jupiter, time) plot(jupiter_lon, "Jupiter Geo Lon", color.yellow) plot(jupiter_decl, "Jupiter Decl", color.red) Retrograde detection: bool mercury_retro = eph.is_retrograde(eph.Planet.Mercury, time) bgcolor(mercury_retro ? color.new(color.red, 90) : na) Moon nodes and declination: float north_node = eph.get_mean_north_node_lon(time) float south_node = eph.get_mean_south_node_lon(time) float moon_decl = eph.get_declination(time) plot(north_node, "North Node", color.green) plot(south_node, "South Node", color.purple) plot(moon_decl, "Moon Declination", color.orange) Dynamic planet selection from input: string planet_str = input.string("Sun", "Planet", options= ) eph.Planet p = eph.string_to_planet(planet_str) float geo = eph.get_longitude(p, time, true) float helio = eph.get_longitude(p, time, false) float speed = eph.get_speed(p, time) plot(geo, "Geocentric", color.yellow) plot(helio, "Heliocentric", color.blue) plot(speed * 100, "Speed x100", color.white) All functions accept TradingView's `time` variable directly. █ FUNCTIONS Unified API (all planets): `get_longitude(Planet, time, preferGeo)` — geo or heliocentric longitude `get_declination(Planet, time)` — equatorial declination `get_speed(Planet, time)` — longitude speed (°/day) `is_retrograde(Planet, time)` — true when retrograde `string_to_planet(string)` — name to enum Averages : `get_avg6_geo_lon` / `get_avg6_helio_lon` — Mercury–Saturn `get_avg8_geo_lon` / `get_avg8_helio_lon` — Mercury–Neptune Moon (direct access): `get_geo_ecl_lon(time)` · `get_geo_ecl_lat(time)` · `get_declination(time)` `get_mean_north_node_lon(time)` · `get_mean_south_node_lon(time)` `get_true_north_node_lon(time)` · `get_true_south_node_lon(time)` `get_north_node_declination(time)` · `get_south_node_declination(time)` █ LIMITATIONS • Truncated series — sub-degree accuracy, not sub-arcsecond. More than sufficient for ingress timing and aspect work. • Validated against DE440 across 250 years (1850–2100). Over this full span, the worst-case VSOP87 planet (Uranus) is 0.017° RMS / 0.043° max error. Ingress dates manually verified back to the late 1800s with consistent accuracy. • Pluto uses Meeus series, limited to ±1 century from J2000. • Moon has no speed function. █ ACKNOWLEDGMENTS Coefficient validation was made possible by Greg Miller's VSOP87 multi-language project, which provides the complete VSOP87D coefficient tables in accessible formats. His work converting the original Fortran data files into CSV/JSON for multiple languages was essential for identifying the L1 precession errors in the original libraries. Miller released this work into the public domain. github.com/gmiller123456/vsop87-multilang References : • Meeus, Jean. Astronomical Algorithms (2nd Ed., 1998) • Bretagnon & Francou. VSOP87 Solutions (Astronomy & Astrophysics, 1988) • Chapront-Touzé & Chapront. ELP2000-82 (1983) █ OPEN SOURCE MIT License — part of the Blueprint Research open-source toolkit. Source code on GitHub get_geo_ecl_lon(time_)   Returns geocentric ecliptic longitude of the Moon.   Parameters:      time_ (float)   Returns: (float) Longitude in degrees, range [0, 360). get_geo_ecl_lat(time_)   Returns geocentric ecliptic latitude of the Moon.   Parameters:      time_ (float)   Returns: (float) Latitude in degrees. get_obliquity_j(time_)   Returns mean obliquity of the ecliptic.   Parameters:      time_ (float)   Returns: (float) Obliquity in degrees. get_declination(time_)   Returns geocentric equatorial declination of the Moon.   Parameters:      time_ (float)   Returns: (float) Declination in degrees, range where positive is north. get_declination(p, t)   Returns planetary geocentric equatorial declination.   Parameters:      p (series Planet) : (Planet) Planet to query.      t (float) : (float) Unix timestamp in milliseconds (use built-in 'time' variable).   Returns: (float) Geocentric declination in degrees, range where positive is north. @note Declination is always geocentric (no heliocentric equivalent in library). get_mean_north_node_lon(time_)   Returns mean longitude of the Moon's North Node (ascending node).   Parameters:      time_ (float)   Returns: (float) Longitude in degrees, range [0, 360). @note Mean node is a simple averaged calculation, reducing computational error. Used for declination calculations. get_mean_south_node_lon(time_)   Returns mean longitude of the Moon's South Node (descending node).   Parameters:      time_ (float)   Returns: (float) Longitude in degrees, range [0, 360). Equals North Node + 180°. get_true_north_node_lon(time_)   Returns true longitude of the Moon's North Node with perturbation corrections.   Parameters:      time_ (float)   Returns: (float) Longitude in degrees, range [0, 360). @note True node includes periodic perturbations but formula is low precision. Consider using mean node for consistency. get_true_south_node_lon(time_)   Returns true longitude of the Moon's South Node with perturbation corrections.   Parameters:      time_ (float)   Returns: (float) Longitude in degrees, range [0, 360). Equals True North Node + 180°. get_north_node_declination(time_)   Returns declination of the Moon's North Node.   Parameters:      time_ (float)   Returns: (float) Declination in degrees, range (bounded by obliquity). @note Uses mean node for calculation (more consistent than true node). get_south_node_declination(time_)   Returns declination of the Moon's South Node.   Parameters:      time_ (float)   Returns: (float) Declination in degrees. Inverse of North Node declination. normalizeLongitude(lon)   Normalizes any longitude value to the range [0, 360) degrees.   Parameters:      lon (float) : (float) Longitude in degrees (can be any value, including negative or >360).   Returns: (float) Normalized longitude in range [0, 360). string_to_planet(planetStr)   Converts a planet string identifier to Planet enum value.   Parameters:      planetStr (string) : (string) Planet name (case-insensitive). Supports formats: "Sun", "☉︎ Sun", "sun", "SUN"   Returns: (Planet) Corresponding Planet enum. Returns Planet.Sun if string not recognized. @note Supported planet strings: Sun, Moon, Mercury, Venus, Earth, Mars, Jupiter, Saturn, Uranus, Neptune, Pluto get_longitude(p, t, preferGeo)   Returns planetary longitude with automatic coordinate system selection.   Parameters:      p (series Planet) : (Planet) Planet to query.      t (float) : (float) Unix timestamp in milliseconds (use built-in 'time' variable).      preferGeo (bool) : (bool) If true, return geocentric; if false, return heliocentric.   Returns: (float) Longitude in degrees, normalized to range [0, 360). @note Sun and Moon always return geocentric regardless of preference (heliocentric not applicable). get_speed(p, t)   Returns planetary geocentric longitude speed (rate of change).   Parameters:      p (series Planet) : (Planet) Planet to query.      t (float) : (float) Unix timestamp in milliseconds (use built-in 'time' variable).   Returns: (float) Geocentric longitude speed in degrees per day. Negative values indicate retrograde motion. Returns na for Moon. @note Speed is always geocentric (no heliocentric equivalent in library). Moon speed calculation not implemented. get_avg6_geo_lon(t)   get_avg6_geo_lon @description Returns the arithmetic average of the geocentric longitudes for the six outer planets: Mars, Jupiter, Saturn, Uranus, Neptune, and Pluto.   Parameters:      t (float) : (float) Time in Unix timestamp (milliseconds).   Returns: (float) Average geocentric longitude of the six outer planets in degrees, range [0, 360). get_avg6_helio_lon(t)   get_avg6_helio_lon @description Returns the arithmetic average of the heliocentric longitudes for the six outer planets: Mars, Jupiter, Saturn, Uranus, Neptune, and Pluto.   Parameters:      t (float) : (float) Time in Unix timestamp (milliseconds).   Returns: (float) Average heliocentric longitude of the six outer planets in degrees, range [0, 360). get_avg8_geo_lon(t)   get_avg8_geo_lon @description Returns the arithmetic average of the geocentric longitudes for all eight classical planets: Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune, and Pluto.   Parameters:      t (float) : (float) Time in Unix timestamp (milliseconds).   Returns: (float) Average geocentric longitude of all eight classical planets in degrees, range [0, 360). get_avg8_helio_lon(t)   get_avg8_helio_lon @description Returns the arithmetic average of the heliocentric longitudes for all eight classical planets: Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune, and Pluto.   Parameters:      t (float) : (float) Time in Unix timestamp (milliseconds).   Returns: (float) Average heliocentric longitude of all eight classical planets in degrees, range [0, 360). is_retrograde(p, t)   Returns true if the planet is currently in retrograde motion (geocentric speed < 0) == 0 = stationary.   Parameters:      p (series Planet) : The planet to check.      t (float) : Time in Unix timestamp (milliseconds).   Returns: true if the planet is in retrograde, false otherwise.
ספריית Pine Script®
מאת ‎BlueprintResearch‎
2
Lunar Cycle Tracker - (Moon + 3 Mercury Retrogrades)This script overlays the lunar and Mercury retrograde cycles directly onto your chart, helping traders visualize natural timing intervals that may influence market behavior. Key Features: 🌑 New Moon & Full Moon Markers: Vertical lines and labels indicate new and full moon events each month. You can fully customize their colors. 🌗 Last Quarter Moon Fill: A soft pink background highlights the last quarter moon phase (from 7.4 days after the full moon to the next new moon). 🪐 Three Mercury Retrograde Zones: Highlight up to three retrograde periods per year with customizable date inputs and background color. Great for spotting potential reversal or volatility windows. Customization: Moon event dates and colors Manual input for Mercury retrograde periods (year, month, day) Full compatibility with all timeframes (1H, 4H, daily, etc.) Great for astro-cycle traders, Gann-based analysts, or anyone who respects time symmetry in the markets. Fully customizable & works across all timeframes. This tool was created by AngelArt as part of a larger astro-market model using lunar timing and planetary retrogrades for cycle-based market analysis.
אינדיקטור Pine Script®
מאת ‎Angelart‎
2
Solar System in 3D [Astro Tool w/ Zodiac]Hello Traders and Developers, I am excited to announce my latest Open Source indicator. At the core, this is a demonstration of PineScript’s capabilities in Rendering 3D Animations, while at the same time being a practical tool for Financial Astrologists. This 3D Engine dynamically renders all the major celestial bodies with their individual orbits, rotation speeds, polar inclinations and astrological aspects, all while maintaining accurate spatial relationships and perspective. This is a Geocentric model of the solar system (viewed from the perspective of Earth), since that is what most Astrologists use. Thanks to the AstroLib Library created by @BarefootJoey, this model uses the real coordinates of cosmic bodies for every timestamp. This script truly comes to life when using the “Bar Replay” mode in TradingView, as you can observe the relationships between planets and price action as time progresses, with the full animation capabilities as mentioned above. In addition to what I have described, this indicator also displays the orbital trajectories for each cosmic body, and has labels for everything. I have also added the ability to hover on all the labels, and see a short description of what they imply in Astrology. Optional Planetary Aspect Computation This indicator supports all the Major Planetary Aspects, with an accuracy defined by the user (1° by default). Conjunction: 0° Alignment. This draws a RED line starting from the center, and going through both planets. Sextile: 60° Alignment. This draws three YELLOW lines, connecting the planets to each other and to the center. Square: 90° Alignment. This draws three BLUE lines, connecting the planets to each other and to the center. Trine: 120° Alignment. This draws three PURPLE lines, connecting the planets to each other and to the center. Opposition: 180° Alignment. This draws a GREEN line starting from one planet, passing through the center and ending on the second planet. The below image depicts a Top-Down view of the system, with the Moon in Opposition to Venus and with Mars in Square with Neptune . Retrograde Computation This indicator also displays when a planet enters Retrograde (Apparent Backward Motion) by making its orbital trajectory dashed and the planet name getting a red background. The image below displays an example of Jupiter, Saturn, Neptune and Pluto in Retrograde Motion, from the camera perspective of a 65 degree inclination. Optional Zodiac Computation (Tropical and Sidereal) Zodiac represents the relatively stationary star formations that rest along the ecliptic plane, with planets transitioning from one to the next, each with a 30° separation (making 12 in total). I have implemented the option to switch between Tropical mode (where these stars were 2,000 years ago) and Sidereal (where these stars are today). The image below displays the Zodiac labels with clear lines denoting where each planet falls into. While this indicator is deployed in a separate pane, it is trivial to transfer it onto your price chart, just by clicking and dragging the graphics. After that, you can adjust the visuals by dragging the scale on the side, or optimizing model settings. You can also drag the model above or below the price, as shown in the following image: Of course, there are a lot of options to customize this planetary model to your tastes and analytical needs. Aside from visual changes for the labels, colors or resolution you can also disable certain planets that don’t meet your needs as shown below: Once can also infer the current lunar phases using the Aspects between the Sun and Moon. When the Moon is Opposite the Sun that is a Full Moon, while when they are Conjunct that is a New Moon (and sometimes Eclipse). —--------------------------------------------------------------------------- I have made this indicator open source to help PineScript programmers understand how to approach 3D graphics rendering, enabling them to develop ever more capable scripts and continuously push the boundaries of what's possible on TradingView. The code is well documented with comments and has a clear naming convention for functions and variables, to aid developers understand how everything operates. For financial astrologists, this indicator offers a new way to visualize and correlate planetary movements, adding depth and ease to astrological market analysis. Regards, Hawk
אינדיקטור Pine Script®
מאת ‎Alien_Algorithms‎
67
Astro: Celestial Body Channel LinesThis is fork of the previous Astro: Planetary Channel Lines indicator that now includes over a dozen different celestial bodies, made possible after the most recent update of the AstroLib library. Celestial Body Channel Lines is an approach to financial astrology that involves using the positions of the celestial bodies to predict trends and patterns in the stock market. The idea behind celestial body lines is that the positions of the bodies in the sky at the time of a market event can significantly influence that event. The celestial body lines approach involves mapping the bodies' positions onto a stock market graph, with each body's position representing a specific line. These lines are thought to indicate areas of support and resistance, as well as potential turning points in the market. This indicator includes geocentric/heliocentric celestial body lines on the chart for up to two bodies, price scaling & vertical offset, mirror/inversion switch, retrograde highlighting, and aspect recognition with customizable precision.
אינדיקטור Pine Script®
מאת ‎BarefootJoey‎
1
Astro: Celestial Body LongitudesThis is fork of the previous Astro: Planetary Longitudes indicator that now includes over a dozen different celestial bodies, made possible after the most recent update of the AstroLib library . Celestial longitude is a measurement of the position of a celestial body in its orbit around the Sun, expressed in degrees of arc along the plane of the body's orbit. It is one of the fundamental coordinates used in astronomy to describe the position of a planet or other celestial object. The concept of longitude is important in astrology, where it is used to determine the position of the planets in the zodiac. In this context, the longitude is measured along the ecliptic, which is the apparent path of the Sun on the celestial sphere. Astrologers use the position of the planets in the zodiac to make predictions and interpretations about personality traits, life events, earthquakes, market events, and other aspects of human experience. This indicator includes geocentric/heliocentric longitude lines with retrograde identification, Vedic Nakshatras, and astrological zodiac & aspects for each of the celestial bodies. Hover over labels for additional information.
אינדיקטור Pine Script®
מאת ‎BarefootJoey‎
3
Astro: Planetary Aspects v2.0I have updated the excellent script originally written by @BarefootJoey with additional functionality as listed below the script's original description: @BarefootJoey: In astrology, planetary aspects refer to the angles formed between two or more planets in a horoscope or birth chart. These angles are created by the positions of the planets in the sky and are thought to represent a particular energy or influence that can impact events on Earth. The most common planetary aspects are the conjunction (when two planets are in the same position in the zodiac), the opposition (when two planets are direct across from each other in the zodiac), the trine (when two planets are 120 degrees apart in the zodiac), and the square (when two planets are 90 degrees apart in the zodiac). This oscillator plots the current geocentric/heliocentric aspect for up to two planets and features a customizable precision of degree (up to +/- 15 degrees) for each aspect. Additional functionality added in by @Yevolution: 1. Overlay the indicator plot on top of the main chart, with the indicator's scale placed on the left - I found it easier to spot price reactions at a given planetary aspect vs seeing the plot in a separate frame 2. Add options to plot a vertical bar for every occurrence of chosen aspects The script source code has remained open and additional comments have been added by me to explain the changes where relevant. When I get some more spare time I will add a function to enable future planetary aspect events to also be displayed on the chart to make forecasting using this data easier.
אינדיקטור Pine Script®
מאת ‎Yevolution‎
25
Astro: Planetary Channel LinesPlanetary Channel Lines is an approach to financial astrology that involves using the positions of the planets to predict trends and patterns in the stock market. The idea behind planetary lines is that the positions of the planets in the sky at the time of a market event can significantly influence that event. The planetary lines approach involves mapping the planets' positions onto a stock market graph, with each planet's position representing a specific line. These lines are thought to indicate areas of support and resistance, as well as potential turning points in the market. This indicator includes geocentric/heliocentric planetary lines on the chart for up to two planets, price scaling & vertical offset, retrograde highlighting, and aspect recognition with customizable precision.
אינדיקטור Pine Script®
מאת ‎BarefootJoey‎
41
Astro: Celestial CoordinatesCelestial coordinates are a system of measurements used in astronomy and astrology to describe the positions of celestial objects such as stars, planets, and constellations. There are several different celestial coordinates, including right ascension (RA), longitude, latitude, declination, and altitude. Each coordinate has its own astronomical or astrological significance, as outlined below: Right ascension (RA) is a coordinate used to describe the position of an object in the sky along the celestial equator. It is measured in hours, minutes, and seconds and is analogous to longitude on Earth. RA is significant in both astronomy and astrology because it allows astronomers and astrologers to accurately locate celestial objects in the sky. Longitude is a coordinate used to describe the position of a planet or other object in its orbit around the Sun. It is measured in degrees and is significant in astronomy because it allows astronomers to accurately predict the positions of planets and other objects in the solar system. Latitude is a coordinate used to describe the position of an object in the sky relative to the celestial equator. It is measured in degrees and is significant in both astronomy and astrology because it helps astronomers and astrologers to determine the positions of celestial objects in the sky. Declination is a coordinate used to describe the position of an object in the sky relative to the celestial equator, similar to latitude but measured in degrees north or south of the celestial equator. It is significant in astronomy because it allows astronomers to accurately locate objects in the sky. Altitude is a coordinate used to describe the height of an object above the horizon. It is measured in degrees and is significant in both astronomy and astrology because it allows astronomers and astrologers to determine when objects will be visible in the sky and at what angle. In astrology, celestial coordinates are used to create maps of the positions of celestial objects. This indicator plots the corresponding celestial coordinate values for each planet, moon, or sun and labels key turning (pivot) points with a date (& optional time). Hover over labels for additional information.
אינדיקטור Pine Script®
מאת ‎BarefootJoey‎
10
Astro: Planetary SpeedPlanetary speed refers to the rate at which a planet moves along its orbit around the Sun. The speed of a planet can vary depending on its distance from the Sun, and is generally fastest at the point in its orbit where it is closest to the Sun (perihelion) and slowest at the point where it is farthest from the Sun (aphelion). The significance of planetary speeds lies in their astrological interpretation. In astrology, the speed of a planet is thought to influence its energy and influence earthly affairs. Fast-moving planets, such as Mercury and Venus, are believed to have a more immediate and fleeting influence, while slower-moving planets, such as Jupiter and Saturn, are thought to have a more long-lasting and significant impact. Astrologers use the speed of the planets, along with their positions, aspects, and other factors, to interpret their influence. By understanding the energy and symbolism associated with each planet, astrologers can provide insight and guidance to individuals seeking a greater understanding.
אינדיקטור Pine Script®
מאת ‎BarefootJoey‎
1
Astro: Solar SystemA bird's eye view model of the solar system is a simplified representation of our planetary system as seen from above. It can be thought of as a two-dimensional map of the solar system, in which the planets are shown in their approximate heliocentric longitudinal positions relative to the Sun and each other. In this model, the Sun is shown as a large, central emoji, with the planets arranged in orbits around it. The inner planets - Mercury, Venus, Earth, and Mars - are located close to the Sun and inside the asteroid belt, while the outer planets - Jupiter, Saturn, Uranus, Neptune, and Pluto- are located farther out. In a bird's eye view model, some of the details of the solar system are necessarily left out or simplified. For example, the distances between the planets are not to scale, and the orbits are shown as perfect circles rather than the elliptical shapes they actually are. Nonetheless, this model can provide a useful visual real-time representation of the relative heliocentric longitudinal positions (aspects) of the planets in our solar system. 🏅 Shoutout to @LuxAlgo for the circle code!
אינדיקטור Pine Script®
מאת ‎BarefootJoey‎
2
Astro: Planetary Aspect TableIn astrology, planetary aspects refer to the angles formed between two or more planets in a horoscope or birth chart. These angles are created by the positions of the planets in the sky and are thought to represent a particular energy or influence that can impact events on Earth. The most common planetary aspects are the conjunction (when two planets are in the same position in the zodiac), the opposition (when two planets are direct across from each other in the zodiac), the trine (when two planets are 120 degrees apart in the zodiac), and the square (when two planets are 90 degrees apart in the zodiac). This chart overlay displays a real-time table of current interplanetary aspects for all AstroLib celestial body combinations.
אינדיקטור Pine Script®
מאת ‎BarefootJoey‎
9
Astro: Planetary Aspect DatesIn astrology, planetary aspects refer to the angles formed between two or more planets in a horoscope or birth chart. These angles are created by the positions of the planets in the sky and are thought to represent a particular energy or influence that can impact events on Earth. The most common planetary aspects are the conjunction (when two planets are in the same position in the zodiac), the opposition (when two planets are direct across from each other in the zodiac), the trine (when two planets are 120 degrees apart in the zodiac), and the square (when two planets are 90 degrees apart in the zodiac). This chart overlay is a simple companion indicator that highlights aspect dates for the following oscillator:
אינדיקטור Pine Script®
מאת ‎BarefootJoey‎
25
Astro: Planetary AspectsIn astrology, planetary aspects refer to the angles formed between two or more planets in a horoscope or birth chart. These angles are created by the positions of the planets in the sky and are thought to represent a particular energy or influence that can impact events on Earth. The most common planetary aspects are the conjunction (when two planets are in the same position in the zodiac), the opposition (when two planets are direct across from each other in the zodiac), the trine (when two planets are 120 degrees apart in the zodiac), and the square (when two planets are 90 degrees apart in the zodiac). This oscillator plots the current geocentric/heliocentric aspect for up to two planets and features a customizable precision of degree (up to +/- 15 degrees) for each aspect.
אינדיקטור Pine Script®
מאת ‎BarefootJoey‎
9
Astro: Planetary LongitudesPlanetary longitude is a measurement of the position of a planet in its orbit around the Sun, expressed in degrees of arc along the plane of the planet's orbit. It is one of the fundamental coordinates used in astronomy to describe the position of a planet or other celestial object. The concept of planetary longitude is important in astrology, where it is used to determine the position of the planets in the zodiac. In this context, the longitude is measured along the ecliptic, which is the apparent path of the Sun on the celestial sphere. Astrologers use the position of the planets in the zodiac to make predictions and interpretations about personality traits, life events, earthquakes, market events, and other aspects of human experience. This indicator includes geocentric/heliocentric longitude lines with retrograde identification, Vedic Nakshatras, and astrological zodiac & aspects for each of the 9 planets plus the Sun & Moon. Hover over labels for additional information. 🏅Shoutout to @AdzAdama and @Virinchi for all the help with this indicator
אינדיקטור Pine Script®
מאת ‎BarefootJoey‎
16
AstroLibLibrary "AstroLib", or Astro Library, is a collection of public Pinescript functions & calculations for use in astrology & astronomy indicators. Unless noted otherwise, this library was written jointly by @badsector666 and @BarefootJoey. Library "AstroLib" t_(txt)   Parameters:      txt (string) JDNv2(t, withFraction)   Parameters:      t (float)      withFraction (bool) J2K(t)   Parameters:      t (float) J2KtoUnix(TimeInJDN)   Parameters:      TimeInJDN (float) atan2(y, x)   Parameters:      y (float)      x (float) DegSin(x)   Parameters:      x (float) DegCos(x)   Parameters:      x (float) DegTan(x)   Parameters:      x (float) DegArcsin(x)   Parameters:      x (float) DegArccos(x)   Parameters:      x (float) DegArctan(x)   Parameters:      x (float) DegAtan2(y, x)   Parameters:      y (float)      x (float) range2pi(x)   Parameters:      x (float) range360(x)   Parameters:      x (float) gst(days)   Parameters:      days (float) DegDecimal(Degrees, Minutes, Seconds)   Parameters:      Degrees (float)      Minutes (float)      Seconds (float) Rectangular(R, theta, phi, Index)   Parameters:      R (float)      theta (float)      phi (float)      Index (float) rLength(x, y, z)   Parameters:      x (float)      y (float)      z (float) spherical(x, y, z, Index)   Parameters:      x (float)      y (float)      z (float)      Index (float) obliquity(d)   Parameters:      d (float) requatorial(x, y, z, d, Index)   Parameters:      x (float)      y (float)      z (float)      d (float)      Index (float) recliptic(x, y, z, d, Index)   Parameters:      x (float)      y (float)      z (float)      d (float)      Index (float) sequatorial(R, theta, phi, d, Index)   Parameters:      R (float)      theta (float)      phi (float)      d (float)      Index (float) secliptic(R, theta, phi, d, Index)   Parameters:      R (float)      theta (float)      phi (float)      d (float)      Index (float) precess(d1, d2, DEC, RA, Index, ddec, dra)   Parameters:      d1 (float)      d2 (float)      DEC (float)      RA (float)      Index (float)      ddec (float)      dra (float) riset(J2000, DEC, RA, GLat, GLong, Index)   Parameters:      J2000 (float)      DEC (float)      RA (float)      GLat (float)      GLong (float)      Index (float) ssun(d, Index)   Parameters:      d (float)      Index (float) rsun(d, Index)   Parameters:      d (float)      Index (float) sun(d, Index)   Parameters:      d (float)      Index (float) SunLongitude(d, Index)   Parameters:      d (float)      Index (float) Sunrise(J2000, GLat, GLong, Index, altitudex)   Parameters:      J2000 (float)      GLat (float)      GLong (float)      Index (float)      altitudex (float) smoon(dx, Index)   Parameters:      dx (float)      Index (float) rmoon(d, Index)   Parameters:      d (float)      Index (float) tmoon(d, GLat, GLong, Index)   Parameters:      d (float)      GLat (float)      GLong (float)      Index (float) moon(d, Index)   Parameters:      d (float)      Index (float) Element(d, pnum)   Parameters:      d (float)      pnum (int) kepler(m, ecc, eps)   Parameters:      m (float)      ecc (float)      eps (float) rplanet(d, pnumber, Index)   Parameters:      d (float)      pnumber (int)      Index (float) planet(d, pnumber, Index)   Parameters:      d (float)      pnumber (int)      Index (float) altaz(d, DEC, RA, GLat, GLong, Index)   Parameters:      d (float)      DEC (float)      RA (float)      GLat (float)      GLong (float)      Index (float) prise(d, P, GLat, GLong, Index)   Parameters:      d (float)      P (int)      GLat (float)      GLong (float)      Index (float) MoonSize(d)   Parameters:      d (float) Refraction(Temperature_C, Atmospheric_Pressure_mBar, Altitude_Deg)   Parameters:      Temperature_C (float)      Atmospheric_Pressure_mBar (float)      Altitude_Deg (float) MoonRise(d, Longitude, Latitude, Index)   Parameters:      d (float)      Longitude (float)      Latitude (float)      Index (float) f_to_sec(dec)   Parameters:      dec (float) f_to_time(sec)   Parameters:      sec (float) deg_to_time(deg)   Parameters:      deg (float) toDMS(coordinate)   Parameters:      coordinate (float) convertDMS(lat, lng)   Parameters:      lat (float)      lng (float) convlatdec(deg)   Parameters:      deg (float) PlanetName(pnum)   Parameters:      pnum (int) PlanetNameV(pnum)   Parameters:      pnum (int) PlanetSign(pnum)   Parameters:      pnum (int) PlanetColor(pnum)   Parameters:      pnum (int) zodiaccolor(deg)   Parameters:      deg (float) degsign(deg)   Parameters:      deg (float) degsignf(deg)   Parameters:      deg (float) degnash(deg)   Parameters:      deg (float) degname(deg)   Parameters:      deg (float) retrogradesym(deg)   Parameters:      deg (float) degaspsign(deg)   Parameters:      deg (float) degaspname(deg)   Parameters:      deg (float) degaspfull(deg)   Parameters:      deg (float) degaspfullV2(deg)   Parameters:      deg (float) degaspnameV2(deg)   Parameters:      deg (float) degtolowest180(deg)   Parameters:      deg (float) degaspfullapproach(deg)   Parameters:      deg (float) virinchiaspectcol(deg, bull_col, bear_col)   Parameters:      deg (float)      bull_col (color)      bear_col (color) virinchiaspectemo(deg, bull_emo, bear_emo)   Parameters:      deg (float)      bull_emo (string)      bear_emo (string) aspectfastsigndeg(deg)   Parameters:      deg (float) aspectfastfull(deg)   Parameters:      deg (float) aspectslowfull(deg)   Parameters:      deg (float) aspectslowsigndeg(deg)   Parameters:      deg (float) aspectslowsign(deg)   Parameters:      deg (float) aspectsignprecision(deg, precision)   Parameters:      deg (float)      precision (int) aspectsignprecisionV2(deg, precision)   Parameters:      deg (float)      precision (float) aspectsignprecisionV2ext(deg, precision)   Parameters:      deg (float)      precision (float) IPaspectsignprecision(planet1, planet2, precision)   Parameters:      planet1 (float)      planet2 (float)      precision (float) IPaspectsignprecisionFull(planet1, planet2, precision)   Parameters:      planet1 (float)      planet2 (float)      precision (float) IPaspectlineprecision(planet1, planet2, precision, style, width)   Parameters:      planet1 (float)      planet2 (float)      precision (float)      style (string)      width (int) rDeg(deg)   Parameters:      deg (float) AngToCirc(angle)   Parameters:      angle (float) AngToCirc180(angle)   Parameters:      angle (float) sidereal(deg, sidereal)   Parameters:      deg (float)      sidereal (bool) J2000(JDN)   Parameters:      JDN (float) JDN(t, d, tz)   Parameters:      t (float)      d (float)      tz (float) getsun(index, day, dayr, latitude, longitude, tz)   Parameters:      index (int)      day (float)      dayr (float)      latitude (float)      longitude (float)      tz (float) getmoon(index, day, dayr, latitude, longitude)   Parameters:      index (int)      day (float)      dayr (float)      latitude (float)      longitude (float) getplanet(planet, index, day, dayr, latitude, longitude, tz)   Parameters:      planet (int)      index (int)      day (float)      dayr (float)      latitude (float)      longitude (float)      tz (float)
ספריית Pine Script®
מאת ‎BarefootJoey‎
19
Future week Calendar; Each day's custom sessions & LabelsOn-Chart Calendar for the week ahead with 4x customizable intraday sessions (each day with it's own unique sessions) -add your own text labels and optional time/date stamps to each session; for key events of the week. -toggle on/off each individual session. -Choose number of weeks of history to show (default is 0: only show upcoming week. -Works on BTC too (includes Saturday/Sunday sessions). //Notes// ~timestamps and labels anchor to the start of the session box ~when using with default 'weeks back to show' = 0; Session boxes will disappear as price passes through their right hand side. ~to remove the very long indicator status line (due to so many sessions): Go to chart settings >> status line, and under 'indicator' toggle off 'arguments' Example usage: Each day's 4x custom sessions showing; only upcoming week; no labels Example usage: Each day's 4x custom sessions showing; Showing 1 week of history too; no labels
אינדיקטור Pine Script®
מאת ‎twingall‎
3
Gamification IndicatorDo you want your charts to look like a video game? Look no further! Would you rather be an alien racing through a lava tube, a surfer with great white sharks, an airplane flying through the clouds, or some other custom emoji setup of your choice? Traders can choose their own custom player emoji, trend indicator, obstacle emoji, and celestial emoji. This indicator is just for fun and is not intended to be used when making trading decisions. Enjoy! This indicator also contains a live sun/moon emoji that should accurately reflect day/night and can give information about the current moon phases. Shoutout to @citlacom for the public Moon Ephemeris and calculations. Building this indicator was a useful & fun introduction to financial astrology in Pinescript.
אינדיקטור Pine Script®
מאת ‎BarefootJoey‎
2
Gann Seasonal Dates by JayCThis script marks important seasonal dates with a vertical line that Gann used to watch for Trend changes. March 21st June 22nd September 23rd December 22nd And 50% Levels - Minor seasonal dates. February 4th May 6th August 8th November 7th In the settings you can change line colors and toggle the Offset. Offset is the way the script draws lines to show future dates, I offset by 365 so it will show incorrectly at some points in back testing.
אינדיקטור Pine Script®
מאת ‎jaycoin2‎
6
Financial Astrology Juno LongitudeJuno is the 4th largest object in terms of mass in the asteroid belt between Mars and Jupiter, this asteroid is not widely used by financial astrologers but as was demonstrated in our research with Ceres and Vesta, the objects in the asteroid belt seems to be very important for the trend forecast. The zodiacal energy of this objects cannot be ignored for an accurate analysis. Based in BTCUSD historical price data we calculated the daily trend (buy/sell) during the periods where Juno was transiting across different zodiac signs and we found some significant patterns: INDEX:BTCUSD Bullish zodiac signs From 387 days located in Scorpio, price increased 62% of the days. From 316 days located in Capricorn, price increased 64% of the days. From 300 days located in Sagittarius, price increased 56% of the days. From 435 days located in Libra, price increased 55% of the days. Bearish zodiac signs From 200 days located in Taurus, price decreased 56% of the days. From 152 days located in Virgo, price decreased 58% of the days. Note: The Juno longitude indicator is based on an ephemeris array that covers years 2010 to 2030, prior or after this years the data is not available, this daily ephemeris are based on UTC time so in order to align properly with the price bars times you should set UTC as your chart timezone.
אינדיקטור Pine Script®
מאת ‎citlacom‎
2
BB-Pivots-GANN-Levels-stockInshotHello everyone, With help of open source WD gann codes, i combined this study with Bollinger band with entry & exit conditions. For stock Selection you way chose fixed stock list . These levels has been derived from daily WD GANN Astro Levels. === Rules === Long Entry Condition : Price must be above resistance line with Bollinger band blast will be the best entry . You may take the target with the help of this study. Stop loss can be same candle low Short Entry Condition : Price must be below support line with Bollinger band blast will be the best entry . You may take the target with the help of this study. Stop loss can be same candle High Please calculate the Risk Reward with the Future Target Price & Stop loss levels. No Trading Zone Rules - If price is in middle of support & Resistance .one way avoid such trades as it has been observed ,That most of the time stock goes sideways. ===Rules End === study has been kept open source for the understanding the concept. Do your own Research with this study for better understanding with your trading style
אינדיקטור Pine Script®
מאת ‎Stock_Inshot‎
10
Financial Astrology Vesta SpeedVesta (asteroid) speed provides a good indicator to determine the periods of dominant trend. During the direct phase (when the speed accelerated and reached highest value) we can observe that BTCUSD experienced a clear trend, perfect for trend following. In the contrary when speed was decelerating and speed started backward motion (retrograde) the price was in congestion experiencing sideways moves. From statistical analysis we noted that when Vesta speed is in direct motion 56% of the days resulted in price increase. When speed was stationary (starting to move retrograde) we observed that in 62% of the days the price decreased, finally, during retrograde phase in 54% of the days the price increased. Is clear that direct motion also offers more bullish days. However, in the statistical analysis of the price is not evident the price change range, with visual exploration in the chart is clear that when Vesta speed is in direct phase the range of the price is wider, therefore, direct motion provides the most interesting risk/reward ratio. Note: The Vesta speed indicator is based on an ephemeris array that covers years 2010 to 2030, prior or after this years the data is not available, this daily ephemeris are based on UTC time so in order to align properly with the price bars times you should set UTC as your chart timezone.
אינדיקטור Pine Script®
מאת ‎citlacom‎
2
Financial Astrology Vesta DeclinationVesta (asteroid) declination show a strong correlation with the BTCUSD trend, we can clearly see that all the most intense bullish periods have occurred when declination was moving from South to Node direction (when the slope is positive). In the events when declination was moving toward North and have penetrated the zero declination boundary (horizontal dashed line) we can observe a periods where price experienced more volatility. Note: The Vesta declination indicator is based on an ephemeris array that covers years 2010 to 2030, prior or after this years the data is not available, this daily ephemeris are based on UTC time so in order to align properly with the price bars times you should set UTC as your chart timezone.
אינדיקטור Pine Script®
מאת ‎citlacom‎
2