Currently I am using version 2.x of your software for generating data to train a neural network via the endplay API. I do not have CPU/memory limitation on the compute cluster that I use but unfortunately I realized that the dds limits the number of deals for which one wants to calculate the DD Table. Could you please lift this limitation in a more systematic way in DDS3? I heard that you have made some changes in this regard but apparently that would require setting some variables for the number of deals for which one wants to calculate DD Table. Wouldn't be possible to remove this restriction and allow the user to run into hardware limitation issues in case he/she runs DDS for way too many deals? Alternatively, would it be possible for DDS to see how much memory/CPU threads a user has access to and then slice the large deals into reasonable sizes to process in batches so it doesn't crash the job.
Currently I am using version 2.x of your software for generating data to train a neural network via the endplay API. I do not have CPU/memory limitation on the compute cluster that I use but unfortunately I realized that the dds limits the number of deals for which one wants to calculate the DD Table. Could you please lift this limitation in a more systematic way in DDS3? I heard that you have made some changes in this regard but apparently that would require setting some variables for the number of deals for which one wants to calculate DD Table. Wouldn't be possible to remove this restriction and allow the user to run into hardware limitation issues in case he/she runs DDS for way too many deals? Alternatively, would it be possible for DDS to see how much memory/CPU threads a user has access to and then slice the large deals into reasonable sizes to process in batches so it doesn't crash the job.