How to set the contract multiplier for Custom Data

Based on the provided code, it seems that 'Ma' is trying to backtest a trading strategy on the Hang Seng Index Futures using custom data. The custom data is read from a CSV file hosted on a remote server. The data includes date, open, high, low, close, and volume information.

The code appears to be correctly structured for the most part. However, there are a few potential issues that might arise:

1. The HSI class, which is a custom data type, is used to parse the CSV data. The Reader method in this class is responsible for parsing each line of the CSV file. It correctly checks if the line is not empty and if the first character is a digit before proceeding. However, it does not handle potential exceptions that might occur during parsing, such as a ValueError if the data cannot be converted to a float. It would be a good idea to wrap the parsing code in a try-except block to handle potential exceptions.

2. The CustomAlgorithm class is the main algorithm class. It correctly initializes the algorithm, adds the custom data, sets up the indicators, and defines the trading conditions. However, the trading conditions are quite complex and might not always be met, which could lead to infrequent trades. It would be a good idea to review these conditions and adjust them if necessary.

3. The OnData method in the CustomAlgorithm class is responsible for executing trades based on the trading conditions. It correctly checks if the algorithm is still warming up and if the slice contains the required symbol before proceeding. However, it does not handle potential exceptions that might occur during order placement, such as an InsufficientBuyingPowerException if there is not enough cash to place an order. It would be a good idea to wrap the order placement code in a try-except block to handle potential exceptions.

4. The OnData method also updates the stop price of the stop market order if the order has been filled and the new stop price is greater than the old one. However, it does not check if the stop market order is still active before updating it, which could lead to an error if the order has already been canceled or filled. It would be a good idea to check the status of the order before updating it.

5. The OnData method places market orders, stop market orders, and limit orders based on the trading conditions. However, it does not keep track of these orders or cancel them if the trading conditions change. It would be a good idea to keep track of these orders and cancel them if necessary.

Please note that these are potential issues and might not actually cause any problems during backtesting. It would be a good idea to run the backtest and review the results and logs to identify any actual issues.

Figured it out, thought I'd share to help the community since no one posts there answers lol 

// Define custom SymbolProperties
var customProperties = new SymbolProperties(
   description: "E-mini S&P 500",
   quoteCurrency: "USD",
   contractMultiplier: 50,  // HERE Point value (e.g., $50 per point for ES)
   minimumPriceVariation: 0.25M,
   lotSize: 1,
   marketTicker: "ES"
);
// Override the security’s SymbolProperties
// Load Market Hours Database
var marketHoursDb = MarketHoursDatabase.FromDataFolder();
// Get exchange hours for ES futures
var market = Market.CME;  // CME for ES futures
var excsymbol = Futures.Indices.SP500EMini; // ES futures symbol
var securityType = SecurityType.Future;
SecurityExchangeHours exchangeHours = marketHoursDb.GetExchangeHours(market, excsymbol, securityType);
Security indicatorSymbol = AddData<StratGenData>(symbol,customProperties,exchangeHours, Resolution.Daily);