Archived Forum Post
Index of archived forum posts
Question:
In tasks like visual tracking or object detection, "deep features" are often modified to be "target-aware".
: It is critical to exclude the target variable from DFS to prevent label leakage , where the model "cheats" by using future information to predict the present. qtarget.zip
: By selecting only target-active filters, the number of features is significantly reduced, which lowers the computational load while maintaining high accuracy. 3. Malware Analysis and Memory Dumps In tasks like visual tracking or object detection,
In the context of automated feature engineering (using tools like Featuretools), "qtarget" or "target" often refers to the being predicted. qtarget.zip
: To safely include historical values of a target, you must use "cutoff times" to ensure the model only sees data available before the prediction point. 2. Target-Aware Deep Features in Computer Vision
: Researchers extract deep features from volatile memory dumps to generate trusted signatures for malicious processes.
: These features are often used with transfer learning to identify new malware based on behaviors captured during execution in a virtual machine.
The problem is with the "dependency". The only dependency is the Visual C++ Redistributable for Visual Studio 2012. The Chilkat .NET assembly is a mixed-mode assembly, where the inner core is written in C++ and compiles to native code. There is a dependency on the VC++ runtime libs. Given that Visual Studio 2012 is new, it won't be already on most computers. Therefore, it needs to be installed. It can be downloaded from Microsoft here:
Visual C++ Redistributable for Visual Studio 2012
If using a .msi install for your app, it should also be possible to include the redist as a merge-module, so that it's automatically installed w/ your app if needed.
Note: Each version of Visual Studio corresponded to a new .NET Framework release:
VS2002 - .NET 1.0 2003 - .NET 1.1 2005 - .NET 2.0 2008 - .NET 3.5 2010 - .NET 4.0 2012 - .NET 4.5The ChilkatDotNet45.dll is for the .NET 4.5 Framework, and therefore needs the VC++ 2012 runtime to be present on the computer.
Likewise, the ChilkatDotNet4.dll is for the 4.0 Framework and needs the VC++ 2010 runtime.
The ChilkatDotNet2.dll is for the 2.0/3.5 Frameworks and requires the VC++ 2005 runtime. (It is unlikely you'll find a computer that doesn't already have the VC++ 2005 runtime already installed.)