Friday, March 30, 2018
Saturday, March 24, 2018
assembly language float types
assembly language float types
- x86 calling conventions
- x86 Disassembly/Calling Conventions
- x86 Disassembly/Floating Point Numbers
- Common x86 Calling Conventions
- X86 Assembly/Floating Point
- Floating-Point Processing
- Floating Point Assembly Language
- Notes about Floating-Point Numbers in Assembly Language
Friday, March 16, 2018
Saturday, March 10, 2018
symbolic computation
- Solving statistics problems with symbolic C# framework
- Symbolic C# Framework for Vector and Matrix Operations
- A Vector Type for C#
- math.net
- MathLibrary for Matrix and Vector
- Exploring parametric ODE with symbolic C# framework
- Symbolic C# Framework for Vector and Matrix Operations
- Symbolic evaluations and numerical methods
- Dynamic Data Display Getting Started
- Microsoft/InteractiveDataDisplay.WPF
- Editor Component for Physical Applications Data Input
- Unicode subscripts and superscripts
Friday, March 9, 2018
raid 1 set up
I bought HD enclosure: NST-27253-BK. it is from www.vantecusa.com. v1.01. Dual 2.5inch SATA SSD/HDD RAID enclsoure. serial number:0664400409.
specification from box: NexStarGX usb3.0 SATA SSD/HDD RAID enclsoure
- model: NST-27253-BK
- device support:SATA I/II/III SSD/HDD/SDHD
- device size:2 bay for 2.5" 7mm and 9.5mm SSD/HDD/SDHDs
- internal interface: SATA
- external interface: usb3.0 micro-B
- HDD capacity: 2 TB per bay, for a combined total of 4TB.
- power supply: USB AC adapter 5V/2A; micro USB to A, length :23 inches
- weight: 300g
- dimension:130x83x25mm
- system requirements: windows 7/8/10, MACX 10.6 or above. Linux ubuten 10.4(kernel 2.6.38)
Features:
- support Dual 2.5" SATA/I/II/III/SSD/HDD/SDHD
- support JBOD/RAID 0 /RAID 1
- Auto RAID 1 rebuild
- support UASP
- SATA interface support SATA III specification up to 6Gps
instruction to set up:
- power up unit
- wait for the drive to spin up speed
- press and hold the reset button for 3 seconds(HDD LEDS will turn off)
- release the reset button and the built-in controller will activate the RAID or normal mode based on the dip switch setting.
- all new USB storage device need to be intialized, partition and formatted for the operating system you are using before it can store data.
- for windows operating system, use Disk Management
- for OS X, use disk utility to prepare this storage device
- note: on Windows 10, plug in usb to computer, power up. the HDD LED lights are on. it shows current setting(JBOFS). now press reset button for 3 seconds. new drives get disconnected and then connected to computers based on sounds. and then new RAID 1 setting is enabled based on light below RAID 1 setting.
- start Disk Management tool. PC automatically recognizes the uninitialized hard drive. it prompts you to format it. follow the prompts and format the hard drive. no quick format and no enable compression.
for details instruction refer to the FAQ " how to preparing a new storage, hard driver, or SSD for use with a system?" on our website support section at www.vantecusa.com
Hard Drive specifications:HGST TRAVELSTAR hard drive. o=bought on 03/08/2018.
- 1TB. 5400 RPM. 8MB/Mo Cache. 9.5mm.
- S/N: 1V2EYNEM (0S03508)
- 12-2017. made in China
- Bar-code: 05487 18982
Saturday, March 3, 2018
research on class design
research on class design. if we have a legacy software, how to improve it? this article gives some thoughts, then follow these threads, we can move on broader view.
- Discovering Hidden Design
- Coupling and Cohesion
- Structured Design
- Writing code for other people: cognitive psychology and the fundamentals of good software design principles
- code of damned: good website
- How to avoid temporal coupling in C#
- Design for change: Coupling and cohesion in object oriented systems
- All You Need to Know About UASP
- Identifying Object-Oriented Classes
- High Cohesion & Low Coupling using SOLID Principles -- Part 1
- High Cohesion & Low Coupling Using SOLID Principles -- Part 2
- Adaptive Code via C#:
Choosing Structure over Naming
There are many qualities that can make designs better. One that really helps names that have clear meaning in the domain. We can use those names to help us determine the relationship between different parts of our code. Beyond that, we can fall back on the classical ideas of coupling and cohesion — a design is good when it maximizes cohesion and minimizes coupling. Although the justification is rarely noted, it's likely that the concepts of coupling and cohesion are useful to us because they are cognitive aids for understanding unfamiliar things [1]. We can understand only so much at a time, so the pieces we attempt to understand should be small and their dependencies should be clear and few. We should be able to understand a chunk of code by itself. Good naming helps us by giving us a mental handle for the other chunks of code that a particular chunk depends upon. It helps us build up a web of understanding.
There are times, however, when our code has internal clustering in its graph and we can't conceive of good names for the clusters. If that is the case, is it acceptable to choose a poor name and move forward with class extraction? Aren't we making our code a little worse if we do that? Again, everyone has to make their own judgment on a situation-by-situation basis, but it's worth considering that naming is only one aspect of program understanding. Code, in general, becomes more understandable when we are looking at chunks that don't have many dependencies on externals. When we can look at a piece and feel that we can understand it locally, we are more likely to be able to change it correctly. The fact that we don't have a good name for it is regrettable, but there is always the chance that we might find a good name later, or that we might eventually merge the the extracted class back into its original class and find a better to way to refactor. In the meantime, we get the benefit of local understanding. If that understanding is constructive relative to the original state of the code, the refactoring might be worthwhile.
Friday, March 2, 2018
research on scale
research on scale. plan is: plotting, zoom, pan on cp.com. chart engine on Devx. Gigasoft on scale and zoom design.
- ProEssentials v8 Help
- .NET C++ MFC Delphi ActiveX Charting Download
- Chapter 2: C# .NET WinForm Walk-Through VS2010
- WinForm C# 2010 Walkthrough or WinForm C# 2012 Walkthrough
- .NET example code is good place to review too
- .NET deployment is good place to review too
- .NET installation
- Build a Reusable Graphical Charting Engine with C#
- Welcome To JFreeChart!
- Scientific charting control
- n MFC Chart Control with Enhanced User Interface
- High-speed Charting Control
- Scientific charting control
- A simple C# library for graph plotting
- Plot Graphic Library
- Drawing Recurrence Plots with C#
- FPlot, a .NET library for plotting functions and measurement data
- AderPlotter
- Oscilloscope/StripChart Control
- Line Graph Component in C#
- Graphing Calculator in C# with LES
- A Simple Graph Control
- Graph Library
- Autoscaling Graph Control
- A 2D Graph Component With Zoom Capability
- Realtime Chart and Graph in One
- C# 2.0 Graphing Control
- Building a Graph control in 7 easy steps.
- Drawing a Line Graph in GDI+
- GraphDisplay: a Bezier based control for graphing functions and curves
- Graph control
- Tracker - A Windows Form graph control
- Bullet Graphs - A Custom Control - WPF vs. Windows Forms
look at alphabetical listing. focus on "S" section: scale. especially on "scale Symbols".
user's manual=>Chapter 2 WPF WinForm ASP.NET =>
extract class design. study the required minimal property and methods to be a charting component.
need to search graph on cp.com