MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "RecalcLastBarAfter",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "1051": {
                "pageid": 1051,
                "ns": 0,
                "title": "Realtime-History Matching",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "==Understanding Realtime-history matching option==\n \n'''Realtime-history matching''' option allows MultiCharts to synchronize the calculation of studies based on several data series. When using several data series calculation on historical data may differ from real-time calculation. Realtime-history matching option makes historical calculation results closer to real-time. \n\t\nWhen Realtime-history matching option is enabled the signal/indicator is calculated on the latest bar of the main data series and on the currently completed bar of the auxiliary data series. If the auxiliary data series stops updating, the final calculation will be made on the main data series bar that was received immediately after the latest bar of the auxiliary data series.  In this case no further calculation will be performed.\n\n<div style=\"background-color: #E3FBE5;\">Note: If more than one auxiliary data series is used, the latest bar for the calculation will be \nthe one that was completed earlier.</div> \n\nWhen Realtime-history matching option is disabled the signal/indicator is calculated on the basis of the main data series latest bar and current (completed or not) bar of the auxiliary data series. If the auxiliary data series stops updating, the calculation will continue on the basis of the latest bar of the main data series and the open bar of the auxiliary data series.\n\n<div style=\"background-color: #E3FBE5;\">Note: All the following examples are true if script/study/signal/strategy is applied to/based on data series 1.</div> \n\n{|class=\"wikitable\"\n! scope=\"row\" colspan=\"2\"| Realtime-History Matching is  <span style=\"color: red>OFF</span>\n|-\n! style=\"width: 50%; text-align:center;\" | Data 1 Continues Updating, Data 2 Stops Updating\n! style=\"width: 50%; text-align:center;\" | Data 1 Stops Updating, Data 2 Continues Updating\n|-\n| Script will be calculated on data series 1 using the updating values from data series 1 and the latest static available values from data series 2.\n| Script will be calculated on the latest bar of data series 1 and will not be calculated until new ticks/bars come in on data series 1, no matter if data series 2 is updating or not. At the moment of this last calculation of the script the latest values of data series 2 are used.\n|-\n! scope=\"row\" colspan=\"2\"|Realtime-History Matching is <span style=\"color: green>ON</span>\n|-\n! style=\"width: 50%; text-align:center;\" | Data 1 Continues Updating, Data 2 Stops Updating\n! style=\"width: 50%; text-align:center;\" | Data 1 Stops Updating, Data 2 Continues Updating\n|-\n| Script will be calculated on a historical bar of data series 1 and will not be calculated until new ticks/bars come in on data series 2, no matter if data series 1 is updating or not.\n| Script will be calculated on the latest bar of data series 1 and will not be calculated until new ticks/bars come in on data series 1, no matter if data series 2 is updating or not. At the moment of this last calculation of the script the corresponding (not the latest) values of data series 2 are used.\n|}\n\n==Enabling/disabling the Realtime-History Matching option==\n\n===Enabling/disabling the Realtime-History Matching option for indicators===\nTo enable/disable the Realtime-History Matching option:\n# Insert an Indicator.<br>To learn more see [[Using Studies#Inserting Studies|Inserting Studies]] section. \n# Open the '''Format Indicator''' window.<span>{{FormatIndicator}}</span>\n# Click the '''Format''' button.\n# Select the '''Properties''' tab.\n# In the '''Advanced''' section, check/uncheck the '''Realtime-History Matching''' checkbox. \n\n===Enabling/disabling the Realtime-History Matching option for signals===\nTo enable/disable the Realtime-History Matching option for signals:\n# Insert a signal.<br>To learn more see [[Using Studies#Inserting Studies|Inserting Studies]] section. \n# Open the '''Format Objects''' window.<br><span>{{FormatObjectIS}}</span>\n# Select the '''Signals''' tab.\n# Click '''Properties''' to open the '''Strategy Properties''' window.\n# Select the '''Backtesting''' tab.\n# Check/uncheck the '''Realtime-History Matching''' checkbox. \n\n<div style=\"background-color: #E3FBE5;\">Note: The Realtime-History Matching option is enabled by default.</div>\n\n[[Category:Studies]]"
                    }
                ]
            },
            "1222": {
                "pageid": 1222,
                "ns": 0,
                "title": "Reasons of Order Rejection",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "Orders can get rejected due to incorrect settings, or if they don\u2019t meet broker requirements.<br>\nTo find the rejection reason, check the [[Order and Position Tracker]] -> [[Order_and_Position_Tracker#Logs_Tab|Logs]] tab.<br>\n\nBelow you can see the most common reasons and their solutions.<br>\nIf you do not find the received rejection reason in this guide, most likely, you\u2019ll need to contact your broker for more info about your order.\n\n== No security definition has been found for this request ==\n\nThis rejection message occurs due to incorrect symbol and/or symbol mapping settings.<br>\n[[Operating_Symbol_List#Adding_Symbol_from_Data_Vendor_Supplied_List|Re-add symbols from data source]] and/or follow the [[How to Set Up Symbol Mapping]] guide. \n\n<div style=\"background-color: #E3FBE5;\">'''Note''': Symbol mapping between the IB symbol on the chart and the IB symbol at the broker is set up automatically and correctly only if you have added the symbol via symbol lookup (see [[Data Sources Overview|Adding Symbol from Data Vendor Supplied List]]).</div>\n\n== The price does not conform to the minimum price variation for this contract ==\nThis rejection message occurs due to incorrect Price Scale and Min. Movement in the [[Setting Properties#Editing an existing symbol properties|symbol's settings]].<br>\nIn this case, orders can be sent with a price that is not accepted by the broker, since for this particular symbol there is no such price.\n<div style=\"background-color: #E5F6FF;\">'''Example''': You cannot place an order to buy at 1,650.01 for ES symbol, since the nearest available prices for this symbol are 1,650.00 and 1,650.25.</div>\n\n=== Data source = broker ===\n\nIn most cases correct symbol parameters are provided by the data source, so the issue can be resolved by [[Operating_Symbol_List#Adding_Symbol_from_Data_Vendor_Supplied_List|re-adding the symbol from the data source]] and creating a new chart for it.<br>\n\nBut if the provided parameters lead to order rejection, they can be adjusted manually in QuoteManager: double-click the symbol -> Settings tab. \n<div style=\"background-color: #E5F6FF;\">'''Example 1''': If the symbol's price changes from XXX.00 to XXX.05, it means that the Price Scale should be 1/100 and the Min. Movement should be 5.<br>'''Example 2''': If symbol's prices changes from X.123450 to X.123460, it means the Price Scale should be 1/1000000 and the Min. Movement should be 10; or the Price Scale should be 1/100000 and the Min. Movement should be 1.</div>\nAfter adjusting the settings, open a new chart for the symbol.<br>\n\n=== Data source \u2260 broker ===\n\nIf you use [[How_to_Set_Up_Symbol_Mapping|symbol mapping]], you'll need to make sure that chart symbol parameters match broker symbol parameters:\n\n# [[Operating_Symbol_List#Adding_Symbol_from_Data_Vendor_Supplied_List|Re-add both chart and broker symbols from data source]]. If manual adjustments are required, please use examples above.\n# In QuoteManager double-click the broker symbol -> '''Settings''' tab<br>Write down / remember/ take a screenshot of the Instrument Settings: '''Price Scale''', '''Min. Movement''', '''Big Point Value'''. Click '''OK'''\n# Double click the chart/data source symbol -> '''Settings''' tab<br>Set the '''Price Scale''', '''Min. Movement''', '''Big Point Value''' same way they are set for your broker instrument. Click '''OK'''\n# Disconnect the broker profile \n# Delete symbol mapping lines for the problematic symbol and [[How_to_Set_Up_Symbol_Mapping|re-configure symbol mapping]]\n# Open a new chart for the symbol\nIf a new order is placed with an incorrect price, its price will be rounded to the nearest acceptable value.\n\n== Invalid order parameters: Account field is empty ==\nThis rejection message occurs when no account is selected in '''Strategy Properties''' or on the '''Chart Trading Panel'''.\nTrading accounts are selected separately for manual and auto trading.\n* For auto trading please go to '''Format''' -> '''Strategy Properties''' -> '''Auto trading tab''' -> '''Broker Plug-in''' section. Make sure your broker is selected there, then click the gear icon. It might be required to look up/specify the account number depending on your broker there.\n* For manual trading you need to select the account on the '''Chart Trading Panel''' in the '''Account Selector'''.\n\n[[Category:FAQ]]"
                    }
                ]
            }
        }
    }
}