feat(simulation): add quant simulation microservice with virtual backtest broker and replay engine
This commit is contained in:
@@ -0,0 +1,29 @@
|
||||
using System;
|
||||
using System.Collections.Generic;
|
||||
using System.ComponentModel.DataAnnotations;
|
||||
using System.ComponentModel.DataAnnotations.Schema;
|
||||
|
||||
namespace FinlyticSimulation.Database.Entities;
|
||||
|
||||
/// <summary>
|
||||
/// A saved, named-by-(Isin, StrategyKey) set of tunable indicator parameter overrides (see
|
||||
/// <c>TechnicalContext.ParameterOverrides</c>), so a parameter set found useful via repeated backtest
|
||||
/// experimentation can be reused without retyping it every time. Purely a backtesting-side convenience - never
|
||||
/// read by live scanning (<c>FinlyticTechnicals.Services.TechnicalScoringEngine</c> never queries this table).
|
||||
/// </summary>
|
||||
[Table("simulation_strategy_parameters")]
|
||||
public class SimulationStrategyParameterEntity
|
||||
{
|
||||
[Required]
|
||||
[MaxLength(20)]
|
||||
public string Isin { get; set; } = string.Empty;
|
||||
|
||||
[Required]
|
||||
[MaxLength(50)]
|
||||
public string StrategyKey { get; set; } = string.Empty;
|
||||
|
||||
/// <summary>Keyed by <c>"{StrategyKey}.{ParameterName}"</c>, matching <c>TechnicalContext.ParameterOverrides</c> 1:1.</summary>
|
||||
public Dictionary<string, decimal> Parameters { get; set; } = new();
|
||||
|
||||
public DateTime UpdatedAtUtc { get; set; } = DateTime.UtcNow;
|
||||
}
|
||||
Reference in New Issue
Block a user