Spaces:
Running
Running
| <html lang="en" data-content_root="./"> | |
| <head> | |
| <meta charset="utf-8" /> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="generator" content="Docutils 0.18.1: http://docutils.sourceforge.net/" /> | |
| <title>Finding the help you need — Monte Documentation</title> | |
| <link rel="stylesheet" type="text/css" href="_static/pygments.css?v=b76e3c8a" /> | |
| <link rel="stylesheet" type="text/css" href="_static/bootstrap-sphinx.css?v=284a2d1d" /> | |
| <link rel="stylesheet" type="text/css" href="_static/graphviz.css?v=eafc0fe6" /> | |
| <link rel="stylesheet" type="text/css" href="_static/bootstrap-sphinx.css?v=284a2d1d" /> | |
| <link rel="stylesheet" type="text/css" href="_static/mdocbase.css?v=d3d4abf6" /> | |
| <script src="_static/documentation_options.js?v=0c6b0622"></script> | |
| <script src="_static/doctools.js?v=888ff710"></script> | |
| <script src="_static/sphinx_highlight.js?v=dc90522c"></script> | |
| <link rel="index" title="Index" href="genindex.html" /> | |
| <link rel="search" title="Search" href="search.html" /> | |
| <link rel="next" title="Third-Party Tools" href="tools.html" /> | |
| <link rel="prev" title="Monte Coding Recipes" href="recipes/index.html" /> | |
| <script type="text/javascript" src="_static/js/jquery-1.12.4.min.js"></script> | |
| <script type="text/javascript"> | |
| var adjustNavbar = function() { | |
| $('body').css('padding-top', parseInt($('#navbar').css("height"))+10); | |
| } | |
| var patchTables = function() { | |
| $("table.table").removeClass("table").removeAttr("border").addClass("monte-table").attr("border", 0); | |
| } | |
| var addScrollSpy = function() { | |
| $('body').attr( "data-spy", "scroll" ).attr( "data-target", "#sidebar" ).attr( "data-offset", 75 ); | |
| } | |
| $(window).resize( adjustNavbar ); | |
| $(window).on( 'load', adjustNavbar ); | |
| $(window).on( 'load', patchTables ); | |
| $(window).on( 'load', addScrollSpy ); | |
| </script> | |
| <meta charset='utf-8'> | |
| <meta http-equiv='X-UA-Compatible' content='IE=edge,chrome=1'> | |
| <meta name='viewport' content='width=device-width, initial-scale=1.0, maximum-scale=1'> | |
| <meta name="apple-mobile-web-app-capable" content="yes"> | |
| <script type="text/javascript" src="_static/js/jquery-1.12.4.min.js"></script> | |
| <script type="text/javascript" src="_static/js/jquery-fix.js"></script> | |
| <script type="text/javascript" src="_static/bootstrap-3.4.1/js/bootstrap.min.js"></script> | |
| <script type="text/javascript" src="_static/bootstrap-sphinx.js"></script> | |
| </head><body> | |
| <!-- MDNAV: We want to redo the majority of the navigation bar. Since the | |
| 'bootstrap' theme does not do a good job putting it into blocks, we | |
| need to overrite it in its entirety. We copy over the original and | |
| add in our stuff, creating blocks where necessary for our various | |
| sub-themes to override. | |
| --> | |
| <div id="navbar" class="navbar navbar-default navbar-fixed-top"> | |
| <div class="container"> | |
| <div class="navbar-header"> | |
| <!-- .btn-navbar is used as the toggle for collapsed navbar content --> | |
| <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".nav-collapse"> | |
| <span class="icon-bar"></span> | |
| <span class="icon-bar"></span> | |
| <span class="icon-bar"></span> | |
| </button> | |
| <a class="navbar-brand" href="index.html"> | |
| MONTE-171.1-project</a> | |
| </div> | |
| <div class="collapse navbar-collapse nav-collapse"> | |
| <ul class="nav navbar-nav"> | |
| <li class="divider-vertical"></li> | |
| <li><a class="navbar-drop" href="refguide.html">Documentation</a></li> | |
| <li><a class="navbar-drop-menu dropdown-toggle" href="#" data-toggle="dropdown"><span class="caret"></span></a> | |
| <ul class="dropdown-menu"> | |
| <li><a href="source/Monte/index.html">Monte Module</a></li> | |
| <li><a href="source/mpy/index.html">mpy Module</a></li> | |
| <li><a href="auxdata.html">Auxilliary Data</a></li> | |
| <li><a href="http://monte.jpl.nasa.gov/data/current">Default Data</a></li> | |
| <li><a href="extensions/index.html">Extensions</a></li> | |
| <li><a href="math/index.html">Algorithms</a></li> | |
| <li><a href="http://monte.jpl.nasa.gov/doc/sis">SIS</a></li> | |
| <li><a href="tools.html">Tools</a></li> | |
| </ul> | |
| </li> | |
| <li><a href="applications/index.html">Applications</a></li> | |
| <li><a class="navbar-drop" href="ui/index.html">Ops UI</a></li> | |
| <li> | |
| <a class="navbar-drop-menu dropdown-toggle" href="#" data-toggle="dropdown"><span class="caret"></span></a> | |
| <ul class="dropdown-menu"> | |
| <li><a href="ui/index.html">Overview</a></li> | |
| <li><a href="ui/setup/index.html">Data Setup</a></li> | |
| <li><a href="ui/command/index.html">Commands</a></li> | |
| </ul> | |
| </li> | |
| <li><a href="recipes/index.html">Recipes</a></li> | |
| <li><a class="navbar-drop" href="#">Help</a></li> | |
| </ul> | |
| <!-- MDNAV: We override the searchbox to use our custom search engine | |
| --> | |
| <!-- MDNAV: Do not show the search bar on any search-related page | |
| (they will already have one). | |
| --> | |
| <!-- MDNAV: optionally switch on the original search vs ours --> | |
| <!-- MDNAV: This is the original bootstrap theme code --> | |
| <form class="navbar-form navbar-right" action="search.html" method="get"> | |
| <div class="form-group"> | |
| <input type="text" name="q" class="form-control" placeholder="Search" /> | |
| </div> | |
| <input type="hidden" name="check_keywords" value="yes" /> | |
| <input type="hidden" name="area" value="default" /> | |
| </form> | |
| </div> | |
| </div> | |
| </div> | |
| <div class="container"> | |
| <div class="row"> | |
| <div class="col-md-4"> | |
| <div id="sidebar" class="bs-sidenav affix-top" role="complementary" data-spy="affix"> | |
| <div class="nav-heading">Navigation</div> | |
| <div style="float: left;"> | |
| <a class="reference internal" href="recipes/index.html" title="Monte Coding Recipes">⇐ Prev</a> | |
| </div> | |
| <div style="float: right;"> | |
| <a class="reference internal" href="tools.html" title="Third-Party Tools">Next ⇒</a> | |
| </div> | |
| <br> | |
| <ul> | |
| <li><a class="reference internal" href="index.html">⇓ Home</a></li> | |
| </ul> | |
| <div class="nav-heading">Page Contents</div> | |
| <ul> | |
| <li><a class="reference internal" href="#">Finding the help you need</a><ul> | |
| <li><a class="reference internal" href="#check-the-documentation">Check the documentation</a></li> | |
| <li><a class="reference internal" href="#email">email</a></li> | |
| <li><a class="reference internal" href="#frequently-asked-questions">Frequently Asked Questions</a></li> | |
| </ul> | |
| </li> | |
| </ul> | |
| </div> | |
| </div> | |
| <div class="body col-md-9 content" role="main"> | |
| <section id="finding-the-help-you-need"> | |
| <span id="monte-help"></span><h1>Finding the help you need<a class="headerlink" href="#finding-the-help-you-need" title="Link to this heading">¶</a></h1> | |
| <p>Generally, you should follow the three step process described below when you run | |
| into a problem using <a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a>. It may seem tedious as you're just starting out, but | |
| working your problem as described is the quickest and surest way to mastering | |
| <a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a>.</p> | |
| <section id="check-the-documentation"> | |
| <h2>Check the documentation<a class="headerlink" href="#check-the-documentation" title="Link to this heading">¶</a></h2> | |
| <p>All new users are encouraged to work through the introductory material ( | |
| <a class="reference internal" href="intro/index.html#monte-intro"><span class="std std-ref">Introduction</span></a>, <a class="reference internal" href="intro/scripting.html#monte-intro-scripting"><span class="std std-ref">Writing Scripts</span></a>, | |
| and <a class="reference internal" href="intro/coreconcepts.html#monte-intro-concepts"><span class="std std-ref">Core Concepts</span></a>) on the home page. This will give | |
| you a solid footing in some of the most critical <a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a> concepts, and will allow | |
| you to more easily understand more advanced applications of <a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a>.</p> | |
| <p>The first time you use a new <a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a> system, you are encouraged to read about | |
| that system in the <a class="reference internal" href="userguide/index.html#monte-indepth"><span class="std std-ref">Monte In-Depth</span></a> section. | |
| This should provide you with the names of the <a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a> classes relevant to that | |
| system, and an overview of how they work together to solve problems. For | |
| instance, the first time you attempt to set up a non-trivial trajectory | |
| integration, reading through the <a class="reference internal" href="userguide/integ/index.html#monte-indepth-integ"><span class="std std-ref">Integrated Trajectories and Equations</span></a> section will | |
| show you how to properly configure your force models, set up the integrator, | |
| run the propagation interactively, etc.</p> | |
| <p>Once you know the class names that you will be using, you can go into the | |
| <a class="reference internal" href="refguide.html#monte-refguide"><span class="std std-ref">reference documentation</span></a> for detailed information on | |
| how to use the classes. The classes can be easily found by either searching on | |
| their name in the <a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a> searchbar, or looking them up alphabetically in the | |
| index.</p> | |
| </section> | |
| <hr class="docutils" /> | |
| <section id="email"> | |
| <h2>email<a class="headerlink" href="#email" title="Link to this heading">¶</a></h2> | |
| <p>If you're unable to solve your problem via the documentation, it's | |
| very possible you've encountered a bug. You can file a bug by sending an | |
| email to <a class="reference external" href="mailto:mdn_software%40jpl.nasa.gov">mdn_software<span>@</span>jpl<span>.</span>nasa<span>.</span>gov</a> . Some guidelines when reporting a bug:</p> | |
| <ol class="arabic simple"> | |
| <li><p>Prefix the email subject with 'BUG: ' (no quotes).</p></li> | |
| <li><p>Try and include as much detail about the problem as possible, | |
| <em>including any error messages</em> and the machine and operating system.</p></li> | |
| <li><p>Be sure to specify the version of <a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a> you are running. The output of | |
| <code class="docutils literal notranslate"><span class="pre">mpython</span> <span class="pre">--version</span></code> is ideal.</p></li> | |
| <li><p>If possible, include some short scripts that highlight the problem.</p></li> | |
| </ol> | |
| </section> | |
| <section id="frequently-asked-questions"> | |
| <h2>Frequently Asked Questions<a class="headerlink" href="#frequently-asked-questions" title="Link to this heading">¶</a></h2> | |
| <ol class="arabic simple"> | |
| <li><p><a class="reference internal" href="#faq-error"><span class="std std-ref">How do I read a Monte error message?</span></a></p></li> | |
| <li><p><a class="reference internal" href="#faq-stackoverflow"><span class="std std-ref">What is a good website for general programming questions and tips?</span></a></p></li> | |
| <li><p><a class="reference internal" href="#faq-whypython"><span class="std std-ref">Why is Monte written in Python (instead of some other language)?</span></a></p></li> | |
| <li><p><a class="reference internal" href="#faq-montevspython"><span class="std std-ref">What is the difference between Monte and the standard Python language?</span></a></p></li> | |
| </ol> | |
| <hr class="docutils" /> | |
| <p id="faq-error"><strong>How do I read a Python / Monte error message?</strong></p> | |
| <blockquote> | |
| <div><p>Python error messages (and <a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a> error messages) are structured in three | |
| sections. The very top of the error message tells you where in the failed | |
| application the error occurred (green below). The next section traces down the | |
| stack of called functions to the actual origin of the error (red). Finally, | |
| there is a description of the actual error at the very bottom, along with the | |
| error type (yellow, error type in this case is "ValueError").</p> | |
| <figure class="align-default"> | |
| <img alt="_images/Help_FAQerrorMsg.png" src="_images/Help_FAQerrorMsg.png" /> | |
| </figure> | |
| <p>So how can you use this information to track down your error? Well, usually | |
| the first step is to read the description of the error from the bottom of | |
| the message. In this case "can not convert string to float: h", doesn't seem | |
| very useful (of course you can't convert the letter "h" to a float!), but | |
| often times this description will have very helpful information. One piece of | |
| information that is useful is that the error seems to be color related - it | |
| occurred in a module called "colors.py", in function named "to_rgba", so it | |
| sounds like it could be an error in some kind of color conversion. Next we | |
| go to the line in our script that actually triggered the error. Here we see | |
| that <code class="docutils literal notranslate"><span class="pre">ax.scatter</span></code> is trying to plot data, and it is specifying a color that | |
| seems dicey (is chrome even a color)? Indeed, this is the source of the error | |
| and changing the color specification to something more reasonable (red) | |
| resolves the issue.</p> | |
| </div></blockquote> | |
| <p id="faq-stackoverflow"><strong>What is a good website for general programming questions and tips?</strong></p> | |
| <blockquote> | |
| <div><p>Stackoverflow is an excellent Q/A site for general programming questions. | |
| However, since <a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a> is a JPL proprietary software package, you won't | |
| find any tips concerning <a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a> there.</p> | |
| </div></blockquote> | |
| <p id="faq-whypython"><strong>Why is Monte written in Python (instead of some other language)?</strong></p> | |
| <blockquote> | |
| <div><p>The core libraries of <a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a> are written in C++ for speed. They are wrapped | |
| and presented to the user in Python for usability, and also because of the | |
| wide variety of excellent, interoperable Python packages available for | |
| use along side <a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a> (like matplotlib, pandas, NumPy / SciPy, etc).</p> | |
| </div></blockquote> | |
| <p id="faq-montevspython"><strong>What is the difference between Monte and the standard Python language?</strong></p> | |
| <blockquote> | |
| <div><p><a class="reference internal" href="source/Monte/index.html#monte"><span class="std std-ref">Monte</span></a> is a standard Python package, and can be used in conjunction with the | |
| entire standard library and any other standard 3rd party Python package.</p> | |
| </div></blockquote> | |
| </section> | |
| </section> | |
| </div> | |
| </div> | |
| </div> | |
| <footer class="footer"> | |
| <div class="container"> | |
| <p class="pull-right"> | |
| <a href="#">Back to top</a> | |
| </p> | |
| <p> | |
| © Copyright 2024, Caltech / Jet Propulsion Laboratory..<br/> | |
| The technical data in this document is controlled under the U.S. | |
| Export Regulations; release to foreign persons may require an | |
| export authorization.<br> | |
| Last updated on Nov 08, 2024.<br/> | |
| </p> | |
| </div> | |
| </footer> | |
| <!-- Piwik --> | |
| <script type="text/javascript"> | |
| var _paq = _paq || []; | |
| _paq.push(["setDocumentTitle", document.domain + "/" + document.title]); | |
| _paq.push(["setCookieDomain", "*.monte.jpl.nasa.gov"]); | |
| _paq.push(["setDomains", ["*.monte.jpl.nasa.gov"]]); | |
| _paq.push(['trackPageView']); | |
| _paq.push(['enableLinkTracking']); | |
| (function() { | |
| var u=(("https:" == document.location.protocol) ? "https" : "http") + "://monte/analytics/"; | |
| _paq.push(['setTrackerUrl', u+'piwik.php']); | |
| _paq.push(['setSiteId', 2]); | |
| var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0]; g.type='text/javascript'; | |
| g.defer=true; g.async=true; g.src=u+'piwik.js'; s.parentNode.insertBefore(g,s); | |
| })(); | |
| </script> | |
| <noscript><p><img src="http://monte.jpl.nasa.gov/analytics/piwik.php?idsite=2" style="border:0;" alt="" /></p></noscript> | |
| <!-- End Piwik Code --> | |
| </body> | |
| </html> |