20060224- All about pixel colors: Reference information

本文总结了在MATLAB中控制图像像素颜色的所有关键因素,包括图像CData维度、类、映射、轴限和图例,特别关注真彩色图像与直接索引图像的差异。

原文:http://blogs.mathworks.com/steve/2006/02/24/all-about-pixel-colors-reference-information/

In this posting I want to summarize all of the factors that control image pixel colors in MATLAB. This information is in the MATLAB documentation, but it is scattered around in several locations. If this is way too much detail for you, that's OK - just come on back next week!

image - CData dimensionality
  • If the image CData is three-dimensional, with the size of the third dimension equal to 3, then the CData values are taken to represent RGB values directly. No other image, axes, or figure properties affect the displayed colors. We sometimes call these "truecolor images."
  • If the image CData is two-dimensional, then the image display colors come from the figure colormap. CData values are used (either directly or in scaled form) as lookup indices into the colormap.
image - CData class
  • For truecolor images, the class of the CData array (uint8, uint16, or double) affects which values are displayed as white. The triple [0 0 0] is always black. For double CData, [1 1 1] is white. For uint8 CData, [255 255 255] is white. For uint16 CData, [65535 65535 65535] is white.
  • For direct indexed images, the class of the CData array affects the indexing operation. For double CData arrays, the value 1 corresponds to the first colormap color. For uint8 or uint16 CData arrays, the value 0 corresponds to the first colormap color.
image - CDataMapping

If the image CData is two-dimensional, then the image display colors come from the figure's colormap, and the image CDataMapping property controls how the colormap lookup is done.

  • If CDataMapping is 'direct', then CData values are used directly as lookup indices into the colormap.
  • If CDataMapping is 'scaled', then CData values are scaled to form lookup indices into the colormap.

For truecolor images, the CDataMapping property has no effect on the displayed pixel colors.

axes - CLim

If the image CData is two-dimensional, and if the image CDataMapping is scaled, then the two-element axes CLim property determines the scaling function. The first element gives the value that maps to the first colormap color, and the second element gives the value that maps to the last colormap color.
For truecolor images, or if the image CDataMapping property is 'direct', the CLim property has no effect on the displayed pixel colors.

figure - Colormap

If the image CData is two-dimensional, then all displayed pixel colors come from the figure Colormap.
For truecolor images, the Colormap property has no effect on the displayed pixel colors.

2025-10-24T06:14:45.483589Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2025-10-24T06:14:45.487190Z 0 [Note] C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe (mysqld 5.7.43-log) starting as process 2792 ... 2025-10-24T06:14:45.499521Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2025-10-24T06:14:45.500924Z 0 [Note] InnoDB: Uses event mutexes 2025-10-24T06:14:45.501775Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier 2025-10-24T06:14:45.503093Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 2025-10-24T06:14:45.509869Z 0 [Note] InnoDB: Number of pools: 1 2025-10-24T06:14:45.510876Z 0 [Note] InnoDB: Not using CPU crc32 instructions 2025-10-24T06:14:45.516358Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M 2025-10-24T06:14:45.739511Z 0 [Note] InnoDB: Completed initialization of buffer pool 2025-10-24T06:14:45.866688Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 2025-10-24T06:14:45.917325Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1818072334033 2025-10-24T06:14:45.919665Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1818072343203 2025-10-24T06:14:46.501026Z 0 [Note] InnoDB: Database was not shutdown normally! 2025-10-24T06:14:46.502853Z 0 [Note] InnoDB: Starting crash recovery. 2025-10-24T06:14:53.325953Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2025-10-24T06:14:53.328050Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2025-10-24T06:14:53.331419Z 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2025-10-24T06:14:53.341449Z 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB. 2025-10-24T06:14:53.377635Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. 2025-10-24T06:14:53.379973Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active. 2025-10-24T06:14:53.382232Z 0 [Note] InnoDB: Waiting for purge to start 2025-10-24T06:14:53.434201Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 7651ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.) 2025-10-24T06:14:53.434424Z 0 [Note] InnoDB: 5.7.43 started; log sequence number 1818072343203 2025-10-24T06:14:53.440369Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=3] log sequence number 1818075015616 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.440496Z 0 [Note] InnoDB: Loading buffer pool(s) from D:\MySql\data\ib_buffer_pool 2025-10-24T06:14:53.444882Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.454213Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=2] log sequence number 1818075015133 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.457121Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.459265Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=13] log sequence number 1818075023156 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.459333Z 0 [Note] Plugin 'FEDERATED' is disabled. 2025-10-24T06:14:53.461391Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=4] log sequence number 1818074852082 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.464302Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.468966Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=8883] log sequence number 1818075644951 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.469327Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.478059Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.481293Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=5] log sequence number 1818074822726 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.488992Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.493841Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=8] log sequence number 1818073611600 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.496594Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.499300Z 0 [ERROR] InnoDB: Page [page id: space=488, page number=3] log sequence number 1818075769646 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.500195Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=22] log sequence number 1818074006086 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.503793Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.505862Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.513791Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=23] log sequence number 1818074993296 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.515785Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.524243Z 0 [ERROR] InnoDB: Page [page id: space=488, page number=527] log sequence number 1818080514186 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.528019Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.537996Z 0 [ERROR] InnoDB: Page [page id: space=540, page number=7] log sequence number 1818081166468 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.541042Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.543656Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=31] log sequence number 1818075024348 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.548712Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.554624Z 0 [ERROR] InnoDB: Page [page id: space=540, page number=4] log sequence number 1818081150547 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.558427Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.565031Z 0 [ERROR] InnoDB: Page [page id: space=539, page number=4] log sequence number 1818080173025 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.567157Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=31683] log sequence number 1818075654250 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.567489Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.571042Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.598497Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them. 2025-10-24T06:14:53.601463Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory. 2025-10-24T06:14:53.603981Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher. 2025-10-24T06:14:53.605450Z 0 [ERROR] InnoDB: Page [page id: space=743, page number=0] log sequence number 1818074641633 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.606048Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher. 2025-10-24T06:14:53.609638Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. InnoDB: Dump of the tablespace extent descriptor: len 40; hex 0000000000000000ffffffff0000ffffffff000000000002aaffffffffffffffffffffffffffffff; asc ;2025-10-24T06:14:53.618233Z 0 [ERROR] InnoDB: InnoDB is trying to free page [page id: space=743, page number=8] though it is already marked as free in the tablespace! The tablespace free space info is corrupt. You may need to dump your tables and recreate the whole database! 2025-10-24T06:14:53.622034Z 0 [ERROR] [FATAL] InnoDB: Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.624235Z 0 [Warning] CA certificate ca.pem is self signed. 2025-10-24 14:14:53 0x354c InnoDB: Assertion failure in thread 13644 in file ut0ut.cc line 921 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 2025-10-24T06:14:53.625645Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory. 2025-10-24T06:14:53.628676Z 0 [Note] Server hostname (bind-address): '*'; port: 3308 2025-10-24T06:14:53.629979Z 0 [Note] IPv6 is available. 2025-10-24T06:14:53.630668Z 0 [Note] - '::' resolves to '::'; 2025-10-24T06:14:53.632389Z 0 [Note] Server socket created on IP: '::'. 2025-10-24T06:14:53.747077Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=16384] log sequence number 1818075741603 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.751073Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.924848Z 0 [Note] Failed to start slave threads for channel '' 2025-10-24T06:14:54.002381Z 0 [Note] Event Scheduler: Loaded 0 events 2025-10-24T06:14:54.003266Z 0 [Note] C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe: ready for connections. Version: '5.7.43-log' socket: '' port: 3308 MySQL Community Server (GPL) 2025-10-24T06:14:54.063857Z 0 [ERROR] InnoDB: Page [page id: space=28, page number=0] log sequence number 1818073721575 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:54.067646Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:54.073181Z 0 [ERROR] InnoDB: Page [page id: space=28, page number=4] log sequence number 1818073721575 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:54.076879Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:54.081031Z 0 [ERROR] InnoDB: Page [page id: space=28, page number=5] log sequence number 1818073639109 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:54.083439Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:54.087366Z 0 [ERROR] InnoDB: Page [page id: space=488, page number=0] log sequence number 1818074963526 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:54.089008Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:54.840960Z 0 [Note] InnoDB: Buffer pool(s) load completed at 251024 14:14:54
最新发布
10-25
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值