[Scope4Xi l7.21] [Win8.1] [OpenCL 1.2] [Python 3.3] [Multiprocessing4Xi 17.21] [Studio4Xi l7.21] - [March 29,2015 Ω 4:24 PM]

ΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞ
~ Common Δ ~ Environment Δ ~ Links to DragonXi Δ	~ Keyboard profiles and commands Δ ~ Includes of OpenCL Δ ~ To-be-done Ω	~ New Module Development Δ ~ Memory mapping and Arena4Xi Δ ~ Xi Device API Δ
~ Macros for Trace Messages Δ ~ Getting whole or part of info Δ ~ Nouns4Xi - Model for Command & Control Δ	~ Unresolved temperary Ω ~ 2D Image Objects for {BPU ... GPU ... ZPU} Δ ~ 3D Image Objects for {BPU ... GPU ... ZPU} Δ	~ Context Objects for {BPU ... GPU ... ZPU} Δ ~ State Machine or Thread Δ ~ Sampler Objects for {BPU ... GPU ... ZPU} Δ
~ Actors Δ ~ Picklers Δ ~ Program Objects for {BPU ... GPU ... ZPU} Δ	~ Test Modules Δ ~ Special cases in tracing Δ ~ Kernel Objects for {BPU ... GPU ... ZPU} Δ	~ Tracing Xi Device Modules Δ ~ sense for Ξ ~ sense for Ξ
~ sense for Ξ ~ sense for Ξ ~ sense for Ξ	~ Command Queue Objects for {BPU ... GPU ... ZPU} Δ ~ Buffer Objects for {BPU ... GPU ... ZPU} Δ ~ WEB4Xi Δ	~ Device Objects for {BPU ... GPU ... ZPU} Δ ~ Pickling Δ ~ Actors Δ
~ Parsing Δ ~ Trace (Print4Xi) Δ ~ Nouns for modules Δ	~ Skeleton Δ ~ Version Δ ~ Miscellaneous Δ	~ Sense XML Files Δ ~ Reason XML Files Δ ~ Ace XML Files Δ
~ Test Files Δ ~ Studio4Xi Δ ~ Verbs Δ	~ Event Objects for {BPU ... GPU ... ZPU} Δ ~ Buffers Δ ~ sense for Ξ	~ sense for Ξ ~ sense for Ξ ~ sense for Ξ
~ sense for Ξ ~ sense for Ξ ~ sense for Ξ	~ API Δ ~ import2ball4xi Δ ~ Compiling and testing Δ	~ Special programs Δ ~ Program tags Δ ~ Dragon processing unit Δ
~ Walktrough and Overview Δ ~ Parsing Scope4Xi modules in Studio4Xi Δ ~ Generating automatically programs Δ	~ 041721 conversion ~ DragonΞ Δ ~ Forums Δ	ξ BLOG Δ
ΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞΞ

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Common

Skeleton
ξ »z2skeleton4xi5test.py
ξ »z2skeleton4xi.py
ξ »z2skeleton4xi5test.txt
ξ »sense-z2skeleton4xi5test.xml
ξ »reason-z2skeleton4xi5test.xml
ξ »ace-test-z2skeleton4xi5test.xml
ξ skeleton for Scope4Xi modules - with dragonized tagging

Version
ξ »version4xi.py
ξ each alphabet folder has this module
ξ this makes importing much easier to programs

select: ~[Σ] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Environment

Environment

Command mode

> go2scope <-- may differ depending on workstation and Python version (go3scope4fb <=> "go Python3 scope in fastblack")
E: <-- root drive differs between workstations
cd scope4xi <-- always
cd 041721 <-- release
cd zap <-- always
cd cc <-- always
cd bat <-- always
call autoexec4scope <-- differs between workstations and versions
call version2riika4xi <-- optional (version2riika4xi.bat replaces version4xi.py with version4riika.py in all folder a ... z)
echo ready for dragonized scoping!

autoexec4scope.bat

echo define Environment Variables for Scope4Xi

SET P2AMD="D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64"
echo #1/33 AMD64

SET P2MCORE=E:\sw4xi\Python33
echo #2/33 MULTIPROCESSING4XI

SET P2PYTHON=d:\Python33
echo #3/33 Python

SET P2SCOPE=e:\scope4xi\zap\lib\sw\shot
echo #4/33 Scope4Xi

SET P2STUDIO=E:\Studio4Xi\Python\3.3\src
echo #5/33 Studio4Xi

SET P2VC="D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin"
echo #6/33 Microsoft Visual Studio

SET PATH=.;%P2PYTHON%;%P2MCORE%;%P2VC%;%P2SCOPE%;%P2STUDIO%;%P2AMD%

SET INCLUDE=%P2PYTHON%\include

SET CLASSPATH=.;%P2PYTHON%\lib;%P2OPENCL%\build\lib.win-amd64-3.2\pyopencl\;%P2MCORE%\lib

SET

SETTINGS
ALLUSERSPROFILE=D:\ProgramData
APPDATA=D:\Users\ceo4dragonxi\AppData\Roaming
ATISTREAMSDKROOT=D:\Program Files (x86)\ATI Stream\
ATISTREAMSDKSAMPLESROOT=E:\ATI\
CLASSPATH=.;d:\Python33\lib;\build\lib.win-amd64-3.2\pyopencl\;E:\sw4xi\Python33\lib;E:\Scope4xi\041721\zap\lib\a;E:\Scope4xi\041721\zap\lib\b;E:\Scope4xi\041721\zap\lib\c;E:\Scope4xi\041721\zap\lib\d;E:\Scope4xi\041721\zap\lib\e;E:\Scope4xi\041721\zap\lib\f;E:\Scope4xi\041721\zap\lib\g;E:\Scope4xi\041721\zap\lib\h;E:\Scope4xi\041721\zap\lib\i;E:\Scope4xi\041721\zap\lib\j;E:\Scope4xi\041721\zap\lib\k;E:\Scope4xi\041721\zap\lib\l;E:\Scope4xi\041721\zap\lib\m;E:\Scope4xi\041721\zap\lib\n;E:\Scope4xi\041721\zap\lib\o;E:\Scope4xi\041721\zap\lib\p;E:\Scope4xi\041721\zap\lib\q;E:\Scope4xi\041721\zap\lib\r;E:\Scope4xi\041721\zap\lib\s;E:\Scope4xi\041721\zap\lib\t;E:\Scope4xi\041721\zap\lib\u;E:\Scope4xi\041721\zap\lib\v;E:\Scope4xi\041721\zap\lib\w;E:\Scope4xi\041721\zap\lib\x;E:\Scope4xi\041721\zap\lib\y;E:\Scope4xi\041721\zap\lib\z;E:\Scope4xi\041721\zap\lib\_
CommonProgramFiles=D:\Program Files\Common Files
CommonProgramFiles(x86)=D:\Program Files (x86)\Common Files
CommonProgramW6432=D:\Program Files\Common Files
COMPUTERNAME=FASTBLACK
ComSpec=D:\Windows\system32\cmd.exe
DXSDK_DIR=K:\sw\microsoft\directx\
FP_NO_HOST_CHECK=NO
HOMEDRIVE=D:
HOMEPATH=\Users\ceo4dragonxi
INCLUDE=d:\Python33\include;E:\Scope4xi\041721\zap\lib\a;E:\Scope4xi\041721\zap\lib\b;E:\Scope4xi\041721\zap\lib\c;E:\Scope4xi\041721\zap\lib\d;E:\Scope4xi\041721\zap\lib\e;E:\Scope4xi\041721\zap\lib\f;E:\Scope4xi\041721\zap\lib\g;E:\Scope4xi\041721\zap\lib\h;E:\Scope4xi\041721\zap\lib\i;E:\Scope4xi\041721\zap\lib\j;E:\Scope4xi\041721\zap\lib\k;E:\Scope4xi\041721\zap\lib\l;E:\Scope4xi\041721\zap\lib\m;E:\Scope4xi\041721\zap\lib\n;E:\Scope4xi\041721\zap\lib\o;E:\Scope4xi\041721\zap\lib\p;E:\Scope4xi\041721\zap\lib\q;E:\Scope4xi\041721\zap\lib\r;E:\Scope4xi\041721\zap\lib\s;E:\Scope4xi\041721\zap\lib\t;E:\Scope4xi\041721\zap\lib\u;E:\Scope4xi\041721\zap\lib\v;E:\Scope4xi\041721\zap\lib\w;E:\Scope4xi\041721\zap\lib\x;E:\Scope4xi\041721\zap\lib\y;E:\Scope4xi\041721\zap\lib\z;E:\Scope4xi\041721\zap\lib\_
LGSDIR=D:\Program Files\Logitech Gaming Software\
LOCALAPPDATA=D:\Users\ceo4dragonxi\AppData\Local
LOGONSERVER=\\FASTBLACK
NUMBER_OF_PROCESSORS=4
OS=Windows_NT
P2A=E:\Scope4xi\041721\zap\lib\a
P2AMD="D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64"
P2B=E:\Scope4xi\041721\zap\lib\b
P2C=E:\Scope4xi\041721\zap\lib\c
P2D=E:\Scope4xi\041721\zap\lib\d
P2E=E:\Scope4xi\041721\zap\lib\e
P2F=E:\Scope4xi\041721\zap\lib\f
P2G=E:\Scope4xi\041721\zap\lib\g
P2H=E:\Scope4xi\041721\zap\lib\h
P2I=E:\Scope4xi\041721\zap\lib\i
P2J=E:\Scope4xi\041721\zap\lib\j
P2K=E:\Scope4xi\041721\zap\lib\k
P2L=E:\Scope4xi\041721\zap\lib\l
P2M=E:\Scope4xi\041721\zap\lib\m
P2MCORE=E:\sw4xi\Python33
P2N=E:\Scope4xi\041721\zap\lib\n
P2O=E:\Scope4xi\041721\zap\lib\o
P2P=E:\Scope4xi\041721\zap\lib\p
P2PYTHON=d:\Python33
P2Q=E:\Scope4xi\041721\zap\lib\q
P2R=E:\Scope4xi\041721\zap\lib\r
P2S=E:\Scope4xi\041721\zap\lib\s
P2STUDIO=E:\Studio4Xi\Python\3.3\src
P2T=E:\Scope4xi\041721\zap\lib\t
P2U=E:\Scope4xi\041721\zap\lib\u
P2V=E:\Scope4xi\041721\zap\lib\v
P2VC="D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin"
P2W=E:\Scope4xi\041721\zap\lib\w
P2X=E:\Scope4xi\041721\zap\lib\x
P2Y=E:\Scope4xi\041721\zap\lib\y
P2Z=E:\Scope4xi\041721\zap\lib\z
P2_=E:\Scope4xi\041721\zap\lib\_
Path=.;d:\Python33;E:\sw4xi\Python33;"D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin";E:\Studio4Xi\Python\3.3\src;"D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64";E:\Scope4xi\041721\zap\lib\a;E:\Scope4xi\041721\zap\lib\b;E:\Scope4xi\041721\zap\lib\c;E:\Scope4xi\041721\zap\lib\d;E:\Scope4xi\041721\zap\lib\e;E:\Scope4xi\041721\zap\lib\f;E:\Scope4xi\041721\zap\lib\g;E:\Scope4xi\041721\zap\lib\h;E:\Scope4xi\041721\zap\lib\i;E:\Scope4xi\041721\zap\lib\j;E:\Scope4xi\041721\zap\lib\k;E:\Scope4xi\041721\zap\lib\l;E:\Scope4xi\041721\zap\lib\m;E:\Scope4xi\041721\zap\lib\n;E:\Scope4xi\041721\zap\lib\o;E:\Scope4xi\041721\zap\lib\p;E:\Scope4xi\041721\zap\lib\q;E:\Scope4xi\041721\zap\lib\r;E:\Scope4xi\041721\zap\lib\s;E:\Scope4xi\041721\zap\lib\t;E:\Scope4xi\041721\zap\lib\u;E:\Scope4xi\041721\zap\lib\v;E:\Scope4xi\041721\zap\lib\w;E:\Scope4xi\041721\zap\lib\x;E:\Scope4xi\041721\zap\lib\y;E:\Scope4xi\041721\zap\lib\z;E:\Scope4xi\041721\zap\lib\_
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=AMD64 Family 16 Model 4 Stepping 2, AuthenticAMD
PROCESSOR_LEVEL=16
PROCESSOR_REVISION=0402
ProgramData=D:\ProgramData
ProgramFiles=D:\Program Files
ProgramFiles(x86)=D:\Program Files (x86)
ProgramW6432=D:\Program Files
PROMPT=$P$G
PSModulePath=D:\Windows\system32\WindowsPowerShell\v1.0\Modules\
PUBLIC=D:\Users\Public
SESSIONNAME=Console
SystemDrive=D:
SystemRoot=D:\Windows
TEMP=D:\Users\CEO4DR~1\AppData\Local\Temp
TMP=D:\Users\CEO4DR~1\AppData\Local\Temp
USERDOMAIN=fastblack
USERNAME=ceo4dragonxi
USERPROFILE=D:\Users\ceo4dragonxi
VS100COMNTOOLS=D:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools\
windir=D:\Windows

PATH
PATH=.;
d:\Python33;
E:\sw4xi\Python33;
"D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin";E:\Studio4Xi\Python\3.3\src;"D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64";
E:\Scope4xi\041721\zap\lib\a;E:\Scope4xi\041721\zap\lib\b;E:\Scope4xi\041721\zap\lib\c;E:\Scope4xi\041721\zap\lib\d;E:\Scope4xi\041721\zap\lib\e;
E:\Scope4xi\041721\zap\lib\f;E:\Scope4xi\041721\zap\lib\g;E:\Scope4xi\041721\zap\lib\h;E:\Scope4xi\041721\zap\lib\i;E:\Scope4xi\041721\zap\lib\j;
E:\Scope4xi\041721\zap\lib\k;E:\Scope4xi\041721\zap\lib\l;E:\Scope4xi\041721\zap\lib\m;E:\Scope4xi\041721\zap\lib\n;E:\Scope4xi\041721\zap\lib\o;
E:\Scope4xi\041721\zap\lib\p;E:\Scope4xi\041721\zap\lib\q;E:\Scope4xi\041721\zap\lib\r;E:\Scope4xi\041721\zap\lib\s;E:\Scope4xi\041721\zap\lib\t;
E:\Scope4xi\041721\zap\lib\u;E:\Scope4xi\041721\zap\lib\v;E:\Scope4xi\041721\zap\lib\w;E:\Scope4xi\041721\zap\lib\x;E:\Scope4xi\041721\zap\lib\y;
E:\Scope4xi\041721\zap\lib\z;E:\Scope4xi\041721\zap\lib\_

autoexec4riika.bat

echo define Environment Variables for Scope4Xi

SET P2AMD="C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64"
echo #1/33 AMD64

SET P2MCORE=P:\Sw4Xi\Python33\Lib\multiprocessing4xi
echo #2/33 MULTIPROCESSING4XI

SET P2PYTHON=I:\sw\Python3.3
echo #3/33 Python

SET P2A=P:\Scope4xi\041721\zap\lib\a
SET P2B=P:\Scope4xi\041721\zap\lib\b
SET P2C=P:\Scope4xi\041721\zap\lib\c
SET P2D=P:\Scope4xi\041721\zap\lib\d
SET P2E=P:\Scope4xi\041721\zap\lib\e
SET P2F=P:\Scope4xi\041721\zap\lib\f
SET P2G=P:\Scope4xi\041721\zap\lib\g
SET P2H=P:\Scope4xi\041721\zap\lib\h
SET P2I=P:\Scope4xi\041721\zap\lib\i
SET P2J=P:\Scope4xi\041721\zap\lib\j
SET P2K=P:\Scope4xi\041721\zap\lib\k
SET P2L=P:\Scope4xi\041721\zap\lib\l
SET P2M=P:\Scope4xi\041721\zap\lib\m
SET P2N=P:\Scope4xi\041721\zap\lib\n
SET P2O=P:\Scope4xi\041721\zap\lib\o
SET P2P=P:\Scope4xi\041721\zap\lib\p
SET P2Q=P:\Scope4xi\041721\zap\lib\q
SET P2R=P:\Scope4xi\041721\zap\lib\r
SET P2S=P:\Scope4xi\041721\zap\lib\s
SET P2T=P:\Scope4xi\041721\zap\lib\t
SET P2U=P:\Scope4xi\041721\zap\lib\u
SET P2V=P:\Scope4xi\041721\zap\lib\v
SET P2W=P:\Scope4xi\041721\zap\lib\w
SET P2X=P:\Scope4xi\041721\zap\lib\x
SET P2Y=P:\Scope4xi\041721\zap\lib\y
SET P2Z=P:\Scope4xi\041721\zap\lib\z
SET P2_=P:\Scope4xi\041721\zap\lib\_

echo #4/33 Scope4Xi

SET P2STUDIO=P:\Studio4Xi\Python\3.3\src
echo #5/33 Studio4Xi

SET P2VC="D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin"
echo #6/33 Microsoft Visual Studio

SET PATH=.;%P2PYTHON%;%P2MCORE%;%P2VC%;%P2STUDIO%;%P2AMD%;%P2A%;%P2B%;%P2C%;%P2D%;%P2E%;%P2F%;%P2G%;%P2H%;%P2I%;%P2J%;%P2K%;%P2L%;%P2M%;%P2N%;%P2O%;%P2P%;%P2Q%;%P2R%;%P2S%;%P2T%;%P2U%;%P2V%;%P2W%;%P2X%;%P2Y%;%P2Z%;%P2_%

SET INCLUDE=%P2PYTHON%\include;%P2A%;%P2B%;%P2C%;%P2D%;%P2E%;%P2F%;%P2G%;%P2H%;%P2I%;%P2J%;%P2K%;%P2L%;%P2M%;%P2N%;%P2O%;%P2P%;%P2Q%;%P2R%;%P2S%;%P2T%;%P2U%;%P2V%;%P2W%;%P2X%;%P2Y%;%P2Z%;%P2_%

SET CLASSPATH=.;%P2PYTHON%\lib;%P2MCORE%\lib;%P2A%;%P2B%;%P2C%;%P2D%;%P2E%;%P2F%;%P2G%;%P2H%;%P2I%;%P2J%;%P2K%;%P2L%;%P2M%;%P2N%;%P2O%;%P2P%;%P2Q%;%P2R%;%P2S%;%P2T%;%P2U%;%P2V%;%P2W%;%P2X%;%P2Y%;%P2Z%;%P2_%

SET

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Links to DragonXi

DragonXi local

»Status2scope4Xi
»Multiprocessing4Xi
»Studio4Xi

DragonXi Web
»Multiprocessing4Xi
»Studio4Xi

Web
»Color codes
ξ used to set colors to verbs and actors in multiprocessing4xi

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Keyboard profiles and commands

Keyboard profiles

ξ »Program2Scope4M1
ξ »Program2Scope4M2
ξ »Program2Scope4M3

Commands

go3scope4fb.bat <-- used by a user in command inside his/her folder
echo go3scope4xi!
E:
cd scope4xi
cd 041721
cd zap
cd cc
cd bat
call autoexec4scope
call version2scope4xi
echo ready for dragonized scoping!

autoexec4scope <-- called automatically above
echo define Environment Variables for Scope4Xi

SET P2AMD="D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64"
echo #1/33 AMD64

SET P2MCORE=E:\sw4xi\Python33
echo #2/33 MULTIPROCESSING4XI

SET P2PYTHON=d:\Python33
echo #3/33 Python

SET P2A=E:\Scope4xi\041721\zap\lib\a
SET P2B=E:\Scope4xi\041721\zap\lib\b
SET P2C=E:\Scope4xi\041721\zap\lib\c
SET P2D=E:\Scope4xi\041721\zap\lib\d
SET P2DRAGON=E:\Scope4xi\041721\zap\lib\dragon
SET P2E=E:\Scope4xi\041721\zap\lib\e
SET P2F=E:\Scope4xi\041721\zap\lib\f
SET P2G=E:\Scope4xi\041721\zap\lib\g
SET P2H=E:\Scope4xi\041721\zap\lib\h
SET P2I=E:\Scope4xi\041721\zap\lib\i
SET P2J=E:\Scope4xi\041721\zap\lib\j
SET P2K=E:\Scope4xi\041721\zap\lib\k
SET P2L=E:\Scope4xi\041721\zap\lib\l
SET P2M=E:\Scope4xi\041721\zap\lib\m
SET P2N=E:\Scope4xi\041721\zap\lib\n
SET P2O=E:\Scope4xi\041721\zap\lib\o
SET P2P=E:\Scope4xi\041721\zap\lib\p
SET P2Q=E:\Scope4xi\041721\zap\lib\q
SET P2R=E:\Scope4xi\041721\zap\lib\r
SET P2S=E:\Scope4xi\041721\zap\lib\s
SET P2T=E:\Scope4xi\041721\zap\lib\t
SET P2U=E:\Scope4xi\041721\zap\lib\u
SET P2V=E:\Scope4xi\041721\zap\lib\v
SET P2W=E:\Scope4xi\041721\zap\lib\w
SET P2X=E:\Scope4xi\041721\zap\lib\x
SET P2Y=E:\Scope4xi\041721\zap\lib\y
SET P2Z=E:\Scope4xi\041721\zap\lib\z
SET P2_=E:\Scope4xi\041721\zap\lib\_

echo #4/33 Scope4Xi

SET P2STUDIO=E:\Studio4Xi\Python\3.3\src
echo #5/33 Studio4Xi

SET P2VC="D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin"
echo #6/33 Microsoft Visual Studio

SET PATH=.;%P2PYTHON%;%P2MCORE%;%P2VC%;%P2STUDIO%;%P2AMD%;%P2A%;%P2B%;%P2C%;%P2D%;%P2DRAGON%;%P2E%;%P2F%;%P2G%;%P2H%;%P2I%;%P2J%;%P2K%;%P2L%;%P2M%;%P2N%;%P2O%;%P2P%;%P2Q%;%P2R%;%P2S%;%P2T%;%P2U%;%P2V%;%P2W%;%P2X%;%P2Y%;%P2Z%;%P2_%

SET INCLUDE=%P2PYTHON%\include;%P2A%;%P2B%;%P2C%;%P2D%;%P2E%;%P2F%;%P2G%;%P2H%;%P2I%;%P2J%;%P2K%;%P2L%;%P2M%;%P2N%;%P2O%;%P2P%;%P2Q%;%P2R%;%P2S%;%P2T%;%P2U%;%P2V%;%P2W%;%P2X%;%P2Y%;%P2Z%;%P2_%

SET CLASSPATH=.;%P2PYTHON%\lib;%P2OPENCL%\build\lib.win-amd64-3.2\pyopencl\;%P2MCORE%\lib;%P2A%;%P2B%;%P2C%;%P2D%;%P2E%;%P2F%;%P2G%;%P2H%;%P2I%;%P2J%;%P2K%;%P2L%;%P2M%;%P2N%;%P2O%;%P2P%;%P2Q%;%P2R%;%P2S%;%P2T%;%P2U%;%P2V%;%P2W%;%P2X%;%P2Y%;%P2Z%;%P2_%

SET

version2scope4xi.bat <-- called automatically above
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
cd ..
echo #4/33 E:\scope4xi\041721\zap\cc\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd lib
echo #4/33 E:\scope4xi\041721\zap\lib\
cd v
echo #5/33 E:\scope4xi\041721\zap\lib\v\

dir *.py
copy version4xi.py E:\scope4xi\041721\zap\lib\a\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\b\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\c\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\d\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\dragon\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\e\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\f\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\g\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\h\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\i\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\j\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\k\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\l\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\m\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\n\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\o\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\p\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\q\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\r\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\s\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\t\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\u\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\v\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\w\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\x\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\y\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\z\version4xi.py
copy version4xi.py E:\scope4xi\041721\zap\lib\_\version4xi.py
cd ..
echo #4/33 E:\scope4xi\041721\zap\lib\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd cc
echo #4/33 E:\scope4xi\041721\zap\cc\
cd bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
echo done!

all2core.bat <-- compiles all core programs!
echo compiling all core folders!

call b2core
call c2core
call d2core
call dragon2core
call e2core
call i2core
call k2core
call p2core
call s2core

echo done!

b2core.bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
cd ..
echo #4/33 E:\scope4xi\041721\zap\cc\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd lib
echo #4/33 E:\scope4xi\041721\zap\lib\
cd b
echo #5/33 E:\scope4xi\041721\zap\lib\b\

python buffer4xi.py

cd ..
echo #4/33 E:\scope4xi\041721\zap\lib\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd cc
echo #4/33 E:\scope4xi\041721\zap\cc\
cd bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
echo done!

c2core.bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
cd ..
echo #4/33 E:\scope4xi\041721\zap\cc\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd lib
echo #4/33 E:\scope4xi\041721\zap\lib\
cd c
echo #5/33 E:\scope4xi\041721\zap\lib\c\

python commandqueue4xi.py

python context4xi.py

cd ..
echo #4/33 E:\scope4xi\041721\zap\lib\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd cc
echo #4/33 E:\scope4xi\041721\zap\cc\
cd bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
echo done!

d2core.bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
cd ..
echo #4/33 E:\scope4xi\041721\zap\cc\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd lib
echo #4/33 E:\scope4xi\041721\zap\lib\
cd d
echo #5/33 E:\scope4xi\041721\zap\lib\d\

python device4xi.py

cd ..
echo #4/33 E:\scope4xi\041721\zap\lib\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd cc
echo #4/33 E:\scope4xi\041721\zap\cc\
cd bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
echo done!

dragon2core.bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
cd ..
echo #4/33 E:\scope4xi\041721\zap\cc\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd lib
echo #4/33 E:\scope4xi\041721\zap\lib\
cd dragon
echo #5/33 E:\scope4xi\041721\zap\lib\dragon\

echo [ACK]
python dragon2buffer4xi.py

echo [ACK]
python dragon2commandqueue4xi.py
echo [ACK]
python dragon2commandqueue4xi5test.py > ..\..\work\txt\dragon2commandqueue4xi5test.txt

echo [ACK]
python dragon2context4xi.py

echo [ACK]
python dragon2device4xi.py

echo [ACK]
python dragon2event4xi.py
echo [ACK]
python dragon2event4xi5test.py > ..\..\work\txt\dragon2event4xi5test.txt

echo [ACK]
python dragon2image4xi.py
echo [ACK]
python dragon2image4xi5test.py > ..\..\work\txt\dragon2image4xi5test.txt

echo [ACK]
python dragon2kernel4xi.py
echo [ACK]
python dragon2kernel4xi5test.py > ..\..\work\txt\dragon2kernel4xi5test.txt

echo [ACK]
python dragon2program4xi.py
echo [ACK]
python dragon2program4xi5test.py > ..\..\work\txt\dragon2program4xi5test.txt

echo [ACK]
python dragon2sampler4xi.py
echo [ACK]
python dragon2sampler4xi5test.py > ..\..\work\txt\dragon2sampler4xi5test.txt

echo [ACK]
python dragon3image4xi.py
echo [ACK]
python dragon3image4xi5test.py > ..\..\work\txt\dragon3image4xi5test.txt

echo [ACK]
python version4xi.py

cd ..
echo #4/33 E:\scope4xi\041721\zap\lib\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd cc
echo #4/33 E:\scope4xi\041721\zap\cc\
cd bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
echo done!

e2core.bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
cd ..
echo #4/33 E:\scope4xi\041721\zap\cc\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd lib
echo #4/33 E:\scope4xi\041721\zap\lib\
cd e
echo #5/33 E:\scope4xi\041721\zap\lib\e\

python event4xi.py

cd ..
echo #4/33 E:\scope4xi\041721\zap\lib\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd cc
echo #4/33 E:\scope4xi\041721\zap\cc\
cd bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
echo done!

i2core.bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
cd ..
echo #4/33 E:\scope4xi\041721\zap\cc\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd lib
echo #4/33 E:\scope4xi\041721\zap\lib\
cd i
echo #5/33 E:\scope4xi\041721\zap\lib\h\

python image2d4xi.py

python image3d4xi.py

cd ..
echo #4/33 E:\scope4xi\041721\zap\lib\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd cc
echo #4/33 E:\scope4xi\041721\zap\cc\
cd bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
echo done!

k2core.bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
cd ..
echo #4/33 E:\scope4xi\041721\zap\cc\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd lib
echo #4/33 E:\scope4xi\041721\zap\lib\
cd k
echo #5/33 E:\scope4xi\041721\zap\lib\k\

python kernel4xi.py

cd ..
echo #4/33 E:\scope4xi\041721\zap\lib\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd cc
echo #4/33 E:\scope4xi\041721\zap\cc\
cd bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
echo done!

p2core.bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
cd ..
echo #4/33 E:\scope4xi\041721\zap\cc\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd lib
echo #4/33 E:\scope4xi\041721\zap\lib\
cd p
echo #5/33 E:\scope4xi\041721\zap\lib\p\

python platformids4xi.py

python platforminfo4xi.py

python program4xi.py

cd ..
echo #4/33 E:\scope4xi\041721\zap\lib\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd cc
echo #4/33 E:\scope4xi\041721\zap\cc\
cd bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
echo done!

s2core.bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
cd ..
echo #4/33 E:\scope4xi\041721\zap\cc\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd lib
echo #4/33 E:\scope4xi\041721\zap\lib\
cd s
echo #5/33 E:\scope4xi\041721\zap\lib\s\

python sampler4xi.py

cd ..
echo #4/33 E:\scope4xi\041721\zap\lib\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd cc
echo #4/33 E:\scope4xi\041721\zap\cc\
cd bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
echo done!

Compiling an alpha folder - a2c.bat ... z2c.bat <-- (tests included!)

a2c.bat <-- compiles programs starting with a <-- (tests included!)
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
cd ..
echo #4/33 E:\scope4xi\041721\zap\cc\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd lib
echo #4/33 E:\scope4xi\041721\zap\lib\
cd a
echo #5/33 E:\scope4xi\041721\zap\lib\a\

python apu2buffer4xi.py

python apu2commandqueue4xi.py
python apu2commandqueue4xi5test.py > ..\..\work\txt\apu2commandqueue4xi5test.txt

python apu2context4xi.py

python apu2device4xi.py

python apu2event4xi.py
python apu2event4xi5test.py > ..\..\work\txt\apu2event4xi5test.txt

echo model for dragonxi2image4xi.py and therefore HAS to get compiled and KEPT!
python apu2image4xi.py
python apu2image4xi5test.py > ..\..\work\txt\apu2image4xi5test.txt

python apu2kernel4xi.py
python apu2kernel4xi5test.py > ..\..\work\txt\apu2kernel4xi5test.txt

python apu2program4xi.py
python apu2program4xi5test.py > ..\..\work\txt\apu2program4xi5test.txt

python apu2sampler4xi.py
python apu2sampler4xi5test.py > ..\..\work\txt\apu2sampler4xi5test.txt

python apu3image4xi.py
python apu3image4xi5test.py > ..\..\work\txt\apu3image4xi5test.txt

python version4xi.py

cd ..
echo #4/33 E:\scope4xi\041721\zap\lib\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd cc
echo #4/33 E:\scope4xi\041721\zap\cc\
cd bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
echo done!

all2c.bat <-- compiles all (including tests!)
echo compiling all !

call a2c
call b2c
call c2c
call d2c
call dragon2c
call e2c
call f2c
call g2c
call h2c
call i2c
call j2c
call k2c
call l2c
call m2c
call n2c
call o2c
call p2c
call q2c
call r2c
call s2c
call t2c
call u2c
call v2c
call w2c
call x2c
call y2c
call z2c
call _2c

echo done!

zapimport2ball4xi.bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
cd ..
echo #4/33 E:\scope4xi\041721\zap\cc\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd lib
echo #4/33 E:\scope4xi\041721\zap\lib\
cd z
echo #5/33 E:\scope4xi\041721\zap\lib\z\

python zapimport2ball4xi.py > ..\..\work\txt\zapimport2ball4xi.txt
rem - if you run above, remember to set the desired input and only one at a time in zapimport2ball4xi.py!

cd ..
echo #4/33 E:\scope4xi\041721\zap\lib\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd cc
echo #4/33 E:\scope4xi\041721\zap\cc\
cd bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
echo done!

run4xi.bat <-- work batch
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
cd ..
echo #4/33 E:\scope4xi\041721\zap\cc\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd lib
echo #4/33 E:\scope4xi\041721\zap\lib\
cd z
echo #5/33 E:\scope4xi\041721\zap\lib\z\

python zpu2buffer4xi.py

cd ..
echo #4/33 E:\scope4xi\041721\zap\lib\
cd ..
echo #3/33 E:\scope4xi\041721\zap\
cd cc
echo #4/33 E:\scope4xi\041721\zap\cc\
cd bat
echo #5/33 E:\scope4xi\041721\zap\cc\bat\
echo done!

path2env4xi.bat <-- environment variables
path > ..\..\work\txt\path2env4xi.txt

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Includes of OpenCL

Includes of OpenCL

ξ »Khronos OpenCL API Registry

ξ »OpenCL 1.1 Single Header File for Applications - opencl.h
ξ »opencl.h

ξ »OpenCL 1.1 Platform-Dependent Macros - cl_platform.h
ξ »cl_platform.h

ξ »OpenCL 1.1 Core API Header File - cl.h
ξ »cl_platform.h

ξ »OpenCL 1.1 Extensions Header File- cl_ext.h
ξ »cl_ext.h

ξ »OpenCL 1.1 Khronos OpenCL/Direct3D 10 Extensions Header File - cl_d3d10.h
ξ »cl_d3d10.h

ξ » OpenCL 1.1 Khronos OpenCL/OpenGL Extensions Header File - cl_gl.h
ξ »cl_gl.h

ξ »OpenCL 1.1 Vendor OpenCL/OpenGL Extensions Header File - cl_gl_ext.h
ξ »cl_gl_ext.h

ξ »OpenCL 1.1 C++ Bindings Header File, implementing the C++ Bindings Specification. cl.hpp
ξ »cl.hpp

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ To-be-done

To-be-done

Long line check
ξ check2lines4scope to check if any source file has too long lines

ξ test modules for each device APU ... ZPU
ξ this is the case if thre is only virtual device xi test such as in case of device module!

Arena4Xi

Arena4Xi
ξ »apu2image4xi.py
size2arena = arena2apu.size
buffer2arena = arena2apu.buffer
ξ above might be right i.e. pointer to memory is buffer not Arena4Xi object!
ξ »apu2buffer4xi.py
task4create2apu ['POINTER2BUFFER'] = arena2apu
ξ above might be bug setting to Arena4Xi object!

[1] queue4scope.py with apu...zpu2queue4xi.py modules handling Queue4Xi and introducing put and get functions for control & command data
ξ on the other hand module such as apu2commandqueue4xi.py creates Queue4Xi object with dictionary key 'QUEUE'

[2] pipe4scope.py with apu...zpu2pipe4xi.py modules handling Pipe4Xi and receive and send functions for control & command messages
ξ maybe we need apu2commandpipe4xi.py ...

[3] process4scope.py with apu...zpu2pipe4xi.py modules handling Process4Xi offering processes to all alphabets

[4] acing the discovery that alphabets as system works well and apu APU kind of three letter combinations are unique

[5] developing command and control modules and messages

[6] acing all new nouns »Nouns for modules

Reference counts
ξ 0 <=> object initialized, available, not yet in use by anybody
ξ >=1 <=> in use
ξ < 0 <=> error situation in system, initialize and reset to zero

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ New Module Development

New Module Development

Image Modules Development Example

Using Event Modules
ξ »apu2event4xi.py
ξ »apu2event4xi5test.py
ξ event object for APU as model for image object

(Step 1/33) Edited Image Module
ξ »apu2image4xi.py
ξ replaced event --> image
ξ replaced Event --> Image
ξ replaced EVENT --> IMAGE

(Step 2/33) New Interface

(Step 2A/33) Module Interface
__all__ = [ 'APU2Image4Xi', # NACK 5.31 p76
'create2dimage4apu', # NACK 5.31 p76
...
(Step 2B/33) Class Interface
_exposed_ = (
'create2dimage', # NACK 5.31 p76
...

(Step 3/33) Imports

(Step 3A/33) Standard Imports
import os
...

(Step 3B/33) Scope4Xi Imports
from apu2buffer4xi import APU2Buffer4Xi
...

(Step 3B/33) Multiprocessing Imports
import _multiprocessing

(Step 3B/33) Multiprocessing4Xi Imports
from ace_object4xi import ace_object4xi
...

(Step 4/33) Global Constants
global apu2image4xi
...

(Step 5/33) Functions according to OpenCL Spefication

trace2image4apu
ξ almost identical

set2imagecallback4apu
ξ almost identical

create2dimage4apu
ξ checked that one has to get info from some modules instead of performing get which fetches data
ξ verified create logic comparing to errcode_ret in page 79 (we track each ok and failed step instead of just one return code!)
ξ discovered that device modules did not return CL_DEVICE_IMAGE2D_MAX_WIDTH and CL_DEVICE_IMAGE2D_MAX_HEIGHT because AMD did not support image objects!
ξ »apu2image4xi5test.py
ξ created the first version to test APU 2D images, edited a2c.bat batch command
ξ analyzed apu2image4xi5test.txt, create function passes, set funtion failed
ξ added trace for image functions and its class into print4xi.py

create3dimage4apu
ξ

getsupportedimageformats4apu

read2image4apu
ξ

write2image4apu
ξ

copy2image4apu
ξ

copy2imagetobuffer4apu
ξ

copy2buffer2image4apu
ξ

map2image4apu
ξ

get2imageinfo4apu
ξ

retain2image4apu
ξ

release2image4apu
ξ

(Step 6/33) Class according to OpenCL Spefication
__init__
create2dimage # NACK 5.31 p76
create3dimage # NACK 5.31 p78
getsupportedimageformats # NACK 5.3.2 p82
read2image # NACK 5.3.3 p84
write2image # NACK 5.3.3 p84
copy2image # NACK 5.3.3 p88
copy2imagetobuffer # NACK 5.3.4 p90
copy2buffer2image # NACK 5.3.4 p92
map2image # NACK 5.3.5 p94
get2imageinfo # NACK 5.3.6 p97
retain2image # NACK 5.4.1 p99
release2image # NACK 5.4.1 p99
sense # NACK
reason # NACK
ace # NACK

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Memory mapping and Arena4Xi

Memory mapping and Arena4Xi

ξ »arena4xi.py
ξ buffer attribute set memory map object

ξ »apu2buffer4xi.py
ξ »buffer4xi5test.py
ξ create Arena4Xi objects and use its buffer attribute

ξ »Memory mapped file support
ξ memory mapped objects support operations such as close, find, move, read, read_byt, resize ...

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Xi Device API

Xi Device API

Δ Xi = {APU ... CPU ... GPU ... ZPU}, where Xi depicts virtual device prepresenting all processing units in the system
ξ instead of having to know the best processing unit(s) for each task,
ξ programmers can command the Xi device letting the system to allocate the best processins unit(s)
ξ better performance and balanced resource usage can be achieved this way
ξ money is saved, because the cost of adding new hardware, such as GPU or special processing unit, becomes lower

Buffer Δ
ξ »buffer4xi.py
ξ explore how to handle Xi device for example in __init__ methods - should it create buffer objects to all devices ?
ξ »buffer4xi5test.py
ξ explore how to verify that Xi device has been tested - for example do NOT just use global to get

Command queue Δ
ξ »commandqueue4xi.py
ξ »commandqueue4xi5test.py

Context Δ
ξ »context4xi.py
ξ »context4xi5test.py

Device Δ
ξ »device4xi.py
ξ »device4xi5test.py

Event Δ
ξ »event4xi.py
ξ »event4xi5test.py

Image 2D Δ
ξ »image2d4xi.py
ξ »image2d4xi5test.py

Image 3D Δ
ξ »image3d4xi.py
ξ »image3d4xi5test.py

Kernel Δ
ξ »kernel4xi.py
ξ »kernel4xi5test.py

Platform ID Δ
ξ »platformids4xi.py
ξ »platformids4xi5test.py

Platform Info Δ
ξ »platforminfo4xi.py
ξ »platforminfo4xi5test.py

Program4xi Δ
ξ »program4xi.py
ξ »program4xi5test.py

Sampler Δ
ξ »sampler4xi.py
ξ »sampler4xi5test.py

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Macros for Trace Messages

Macros for Trace Messages

ξ »activated-c
ξ message2print = "{activated" + "; zzzzzzzz-of-ZZZZZZZZ-activated: " + "; time: " + time4xi() + "}"
ξ print4xi(class2print, method2print, message2print)

ξ »Program Macros
ξ »Developer Macros

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Getting whole or part of info

Getting whole or part of info

ξ »apu2image4xi.py
ξ get2imageinfo4apu function returns all or only requested elements and their values
ξ »apu2image4xi5test.py
ξ only height and width of 2D image are being accessed

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Nouns4Xi - Model for Command & Control

Nouns4Xi - Model for Command & Control

Multiprocessing4Xi
ξ »noun4xi.py

function color_nouns4xi
Δ Pipe Channels: consumer & publisher: pipe2zero, one...eight_consumer_channel & pipe2zero, one...eight_publisher_channel
Δ Processes: one for each direction: p2one ...p2eight
Δ Queues: queue zero for main program - queue 1...8 for process 1...8

PROCESS COMMUNICATION CREATING
ξ pipe2zero_consumer_channel, pipe2zero_publisher_channel = Pipe4Xi()
ξ ...
ξ pipe2eight_consumer_channel, pipe2eight_publisher_channel = Pipe4Xi()

ξ queue2zero = Queue4Xi()
ξ ...
ξ queue2eight = Queue4Xi()

COMMAND AND CONTROL MESSAGES PUT AND GET MANOEUVRES
ξ message2put4one = "copy2one"
ξ ...
ξ message2put4eight = "copy2eight"

ξ queue2one.put(message2put4one)
ξ ...
ξ queue2eight.put(message2put4eight)

SEND COMMAND AND CONTROL MESSAGES TO EIGHT PIPES
ξ message2send4one = "copy2one"
ξ ...
ξ message2send4eight = "copy2eight"

ξ pipe2one_publisher_channel.send(message2send4one)
ξ ...
ξ pipe2eight_publisher_channel.send(message2send4eight)

CREATE PROCESSES - ONE FOR EACH DIRECTION OF EIGHT
ξ p2one = Process4Xi(target=charge2one4xi, args=(queue2one, pipe2one_consumer_channel, pipe2one_publisher_channel))
ξ ...
ξ p2eight = Process4Xi(target=charge2eight4xi, args=(queue2eight, pipe2eight_consumer_channel, pipe2eight_publisher_channel))

START PROCESSES - FOR DIRECTIONS ONE TO EIGHT
ξ p2one.start()
ξ ...
ξ p2eight.start()

RUN PROCESSES - FOR DIRECTIONS ONE TO EIGHT
ξ p2one.run()
ξ ...
ξ p2eight.run()

GET ANSWERS FROM QUEUES TO CONTROL MESSAGES - FROM QUEUES OF EACH OF EIGHT PROCESS
ξ message2get4one = queue2one.get() <=> MESSAGE: roger2one
ξ ...
ξ message2get4eight = queue2eight.get() <=> MESSAGE: roger2eight

RECEIVE VIA PIPES ANSWERS TO CONTROL MESSAGE - FROM EACH OF EIGHT PROCESSES
ξ message2receive4one = pipe2one_consumer_channel.recv() <=> CONTROL MESSAGE: roger2one
ξ ...
ξ

CONTROL MESSAGE: roger2eight

RECEIVE INFO ABOUT SUCCESFULL DICTIONARY PUT VIA PIPES FROM EACH PROCESS/DIRECTION - MASTER ONES ONLY
ξ message2receive4one = pipe2one_consumer_channel.recv() <=> queue2one
ξ ...
ξ message2receive4eight = pipe2eight_consumer_channel.recv() <=> queue2eight

GET DICTIONARIES FROM QUEUES ONE ... EIGHT MASTER MODULES
ξ dictionary2get4one = queue2one.get() <=> {1: '0x0y19z', 2: '0x0y39z', 3: '0x0y59z', 4: '0x0y89z', 5: '0x13y14z', 6: '0x13y15z', 7: '0x1y39z', 8: '0x1y59z' ...
ξ ...
ξ dictionary2get4eight = queue2eight.get() <=> {1: '-10x-10y-12z', 2: '-10x-11y-13z', 3: '-10x-3y-27z', 4: '-10x-58y-6z', 5: '-10x-7y-37z', 6: '-11x-1y-27z', 7: '-11x-2y-27z', 8: '-11x-48y-4z' ...

RECEIVE VIA PIPE INFORMATION ABOUT PUT OPERATION OF COORDINATES - AS TO CONFIRM PUT
ONE - LAYERS 10, 100, 200 ... 3300
ξ message2receive4one = pipe2one_consumer_channel.recv() <=> queue2one8shot2one104xi
ξ message2receive4one = pipe2one_consumer_channel.recv() <=> queue2one8shot2one1004xi
ξ ...
ξ message2receive4one = pipe2one_consumer_channel.recv() <=> queue2one8shot2one33004xi
...
EIGHT - LAYERS 10, 100, 200 ... 3300
ξ message2receive4eight = pipe2eight_consumer_channel.recv() <=> queue2eight8shot2eight104xi
ξ message2receive4eight = pipe2eight_consumer_channel.recv() <=> queue2eight8shot2eight1004xi
ξ ...
ξ message2receive4eight = pipe2eight_consumer_channel.recv() <=> queue2eight8shot2eight33004xi

GET COORDINATE DICTIONARY FROM QUEUE
ξ fire2eight104xi = queue2eight.get() <=> {1: '-10x-10y-12z', 2: '-10x-11y-13z', 3: '-10x-3y-27z', 4: '-10x-58y-6z', 5: '-10x-7y-37z', 6: '-11x-1y-27z', 7: '-11x-2y-27z', 8: '-11x-48y-4z' ...

GO THROUGH NOUN2CLUSTER4XI

RETURN NOUN COLOR DICTIONARY

Target Functions for Processes
ξ »charge2one4xi.py
ξ def charge2one4xi(queue2work, channel2consume, channel2publish):
ξ GETTING FROM QUEUE: message2qet4one = queue2work4one.get() <=> copy2one
ξ PUTTING TO QUEUE: queue2work4one.put(message2put4one) <=> roger2one
ξ RECEIVING FROM PIPE CONSUMER CHANNEL: message2receive4one = channel2consume4one.recv() <=> copy2one
ξ SEND DATA TO THE PIPE'S PUBLISHER CHANNEL: channel2publish4one.send(message2send4one) <=> roger2one
ξ USING THE DUMMY PROCESS TO CHARGE: dummy2one = DummyProcess4Xi(target=fire2one4xi, args =(queue2work4one, channel2consume4one, channel2publish4one))
ξ MAIN DUMMY PROCESS OBJECT START: dummy2one.start()
ξ dummy10one = DummyProcess4Xi(target=fire10one4xi, args =(queue2work4one, channel2consume4one, channel2publish4one))
ξ dummy10one.start()
ξ ...
ξ dummy3300one = DummyProcess4Xi(target=fire3300one4xi, args =(queue2work4one, channel2consume4one, channel2publish4one))
ξ dummy3300one.start()

ξ return #Note: because the target function for Process4Xi starts threads, return is possible without waiting results!

Dummy Process i.e. Thread started from target function
ξ »fire2one4xi.py
ξ def fire2one4xi(queue2one, consumer_channel2one, publisher_channel2one) <=>
ξ PUT SHOT TO QUEUE: queue2one.put(shot2one104xi)
ξ INFORM PUT OPERATIONS VIA PIPE'S PUBLISHER CHANNEL: message2send4one = "queue2one" - publisher_channel2one.send(message2send4one)

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Unresolved temperary

Unresolved temperary

image2d4xi.py

ξ »image2d4xi.py
ξ hit the problem can not import create2event4xi
ξ from event4xi import create2event4xi succeeded in the same folder e with event4xi.py !
ξ from event4xi import create2event4xi succeeded when event4xi.py was in the same folder i with image2d4xi.py !
ξ import event4xi <-- OK!
ξ from event4xi import Event4Xi <-- OK!
ξ created bug2c.bat and debugged version4xi.py which seems to work ok i.e. problem might not be path
ξ passed by deleting imports not needed by image2d4xi.py

TRIALS!
ξ »image3d4xi.py
ξ imports Event4Xi and uses its method

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ 2D Image Objects for {BPU ... GPU ... ZPU}

2D Image Objects for {BPU ... GPU ... ZPU}

DRAGON
ξ base processing unit used to automatically generate 2D image objects to other processing units
ξ »dragon2image4xi.py

(1) Find Model - optional
ξ this step is needed when another working source file is used as a model to create source file to handle kernel objects
ξ »apu2image4xi.py
ξ »apu2image4xi5test.py
ξ used as base for kernel objects

(2) Edit Programs - optional
ξ create source files for the processing unit APU
ξ »apu2image4xi.py
ξ »apu2image4xi5test.py
ξ edited Public API comparing to the OpenCL specificatio and removed extra functions and methods
ξ set2kernel4apu, set2kernelcallback4apu and trace2kernel4apu defined as in any Scope4Xi modules (not in OpenCL specs!)

(3) Set Trace for Programs - once
ξ »print4xi.py
ξ both class and function to all kernels {APU ... ZPU} and virtual kernel {xi}
ξ set debug = True if print4xi.py denies trace

(4) Update Pickle Modules - once
ξ »pickle2a4xi.py
...
ξ »pickle2d4xi.py
ξ special DRAGON processing unit!
...
ξ »pickle2z4xi.py

(5) Test Program for APU (reference processing unit)
ξ processing unit could be any, APU was selected here
ξ »apu2image4xi.py
ξ »apu2image4xi5test.py
ξ »apu2image4xi5test.txt
ξ »ace-apu2image4xi5test
ξ »reason-apu2image4xi5test
ξ »sense-apu2image4xi5test

(6) Fetch Programs for APU in Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or there are others reasons to update dragon program
ξ »fetch2scope4xi.py
ξ »version4xi.py
ξ (6a) define apu2image4xi.py and apu2image4xi5test.py as programs to be fetched in kb2fetch dictionary of fetch2scope4xi.py
ξ (6b) check: path2read4xi # path for input source programs
ξ (6c) check: path2write4xi # path for output source programs
ξ (6d) in command mode >go2studio
ξ (6e) >fetch2scope4xi
ξ »apu2image4xi.py
ξ »apu2image4xi5test.py

(7) Generate Dragon modules of Programs for APU to Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or APU has so many changes that a new dragon module is easier to make
ξ (7a) »dragonize2scope4xi.py
ξ (7b) kb2dragonize["apu2image4xi.py"] = "dragon2image4xi.py"
ξ (7c) kb2dragonize["apu2image4xi5test.py"] = "dragon2image4xi5test.py"
ξ (7d) in command mode >dragonize2scope4xi
ξ (7e) »dragon2image4xi.py
ξ (7f) »dragon2image4xi5test.py
ξ (7g) do not delete trace of APU - it has been created in the way that will be dragonize ok

(8) Generate from Dragon Program modules to {BPU,CPU ... ZPU} - mandatory - {APU} must be skipped
ξ ** warning ** do NOT generate for your reference processing unit, in this case APU processing unit is skipped!
ξ you need one good and real processing unit as master and base for other processing unit
ξ although system could generate source code also to your reference processing unit, do NOT let it do it!
ξ if something goes wrong you'll need the source files of your reference processing unit!
ξ generation may tailor code based on each processing unit capabilities and features!
ξ (8a) »generate2kernel4scope.py
ξ (8b) edited generator for program using kernel generator as base
ξ (8c) »print4xi.py
ξ (8d) updated trace for Studio4xi
ξ (8e) »pickle2g4xi.py
ξ (8f) updated pickling
ξ (8g) »actor2g4xi.py
ξ (8h) updated actors

(9) Generate
ξ (9a) »generate2kernel4scope.py
ξ kb2tailor <-- update (if necessary) to generate apu2image4xi.py .. apu2image4xi.py
ξ (9a) »dragon2image4xi.py
ξ (9b) »version4xi.py
ξ (9c) update ActKB4scope dictionary with new module
ξ (9d) ActKB4scope ['z'] ['generate2kernel4scope'] = 'ACK' # FIRST TO GENERATE BY SETTING TO 'ACK'!
ξ (9e) version4xi.py defines which processing unit kernel is to be developed - you generate for one at a time
ξ (9f) replace used output ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib <-- ROOT2TEMP4SCOPE:out\lib (empty)
ξ (9g) either >generate2kernel4scope
ξ (9g) or >python generate2kernel4scope.py > ROOT2JOB4SCOPE:\04711\studio4xi\cc\generate\out\txt\generate2kernel4scope.txt
ξ (9h) check ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\txt\generate2kernel4scope.txt
ξ REMEMBER: version4xi.py ActKB4scope changes for each object and its tester!

(10) Compile one and generate to other processing units
ξ (10a) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\z\zpu2image4xi.py --> ROOT2SCOPE4XI:\041721\zap\lib\z\zpu2image4xi.py
ξ (10b) »zpu2image4xi.py
ξ (10c) compile it!
ξ (10d) ActKB4scope of version4xi.py <-- edit and run for each processing unit - ONE at a time NOT many at the same time!
ξ (10e) take backups from your current Scope4Xi BEFORE proceeding!
ξ (10f) check output programs BEFORE copying them in ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out <-- 25 files in 26 folders!
ξ (10g) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\
ξ (10h) compile all by running all2c - if there are errors you most propably tried to generate several programs in one run!
ξ DONE - you have generated kernel object modules to processing units {BPU ... GPU ...ZPU} and NOT for {APU}

(11) Generate Commandqueue4Xi5test modules as above
ξ (11a) »generate2kernel4scope.py
ξ define test module: kb2tailor ['b'] ['module'] = 'bpu2image4xi5test.py' ... kb2tailor ['z'] ['module'] = 'zpu2image4xi5test.py'
ξ (11b) »version4xi.py
ξ as above ActKB4scope ['b'] ['generate2kernel4scope'] = 'ACK' ... ActKB4scope ['z'] ['generate2kernel4scope'] = 'ACK' one at a time

(14) Copy generated Program modules to Scope4xi
ξ (14a) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\

(15) Update batch files - once
ξ only once - skipped in this version

(16) Compile and test Program modules all processing units
ξ (16a) >all2c in command mode of Scope4xi
ξ (16b) ROOT2SCOPE4XI:\041721\zap\work\txt <-- see that all are updated, check some if any there are FAILED messages
ξ (16c) ROOT2SCOPE4XI:\041721\zap\web\xml <-- see that all are updated and browser some

(17) DONE
ξ backup ROOT2SCOPE4XI:\041721
ξ backup ROOT2JOB4SCOPE:\041721

1) APU reference processing unit ones created with physical processing unit
ξ »apu2image4xi.py
ξ »apu2image4xi5test.py

2) DRAGON processing unit ones created from APU and used to automatically by software to generate software for {BPU ... GPU ... ZPU}
ξ »dragon2image4xi.py
ξ »dragon2image4xi5test.py

3) Commandqueue objects for processing units {BPU ... GPU ... ZPU}
ξ »bpu2image4xi.py
ξ »bpu2image4xi5test.py
ξ BPU generated ones
...
ξ »gpu2image4xi.py
ξ »gpu2image4xi5test.py
ξ GPU generated ones
...
ξ »zpu2image4xi.py
ξ »zpu2image4xi5test.py
ξ ZPU generated ones

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ 3D Image Objects for {BPU ... GPU ... ZPU}

3D Image Objects for {BPU ... GPU ... ZPU}

DRAGON
ξ base processing unit used to automatically generate 3D image objects to other processing units
ξ »dragon3image4xi.py

(1) Find Model - optional
ξ this step is needed when another working source file is used as a model to create source file to handle kernel objects
ξ »apu3image4xi.py
ξ »apu3image4xi5test.py
ξ used as base for kernel objects

(2) Edit Programs - optional
ξ create source files for the processing unit APU
ξ »apu3image4xi.py
ξ »apu3image4xi5test.py
ξ edited Public API comparing to the OpenCL specificatio and removed extra functions and methods
ξ set2kernel4apu, set2kernelcallback4apu and trace2kernel4apu defined as in any Scope4Xi modules (not in OpenCL specs!)

(3) Set Trace for Programs - once
ξ »print4xi.py
ξ both class and function to all kernels {APU ... ZPU} and virtual kernel {xi}
ξ set debug = True if print4xi.py denies trace

(4) Update Pickle Modules - once
ξ »pickle2a4xi.py
...
ξ »pickle2d4xi.py
ξ special DRAGON processing unit!
...
ξ »pickle2z4xi.py

(5) Test Program for APU (reference processing unit)
ξ processing unit could be any, APU was selected here
ξ »apu3image4xi.py
ξ »apu3image4xi5test.py
ξ »apu3image4xi5test.txt
ξ »ace-apu3image4xi5test
ξ »reason-apu3image4xi5test
ξ »sense-apu3image4xi5test

(6) Fetch Programs for APU in Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or there are others reasons to update dragon program
ξ »fetch2scope4xi.py
ξ »version4xi.py
ξ (6a) define apu3image4xi.py and apu3image4xi5test.py as programs to be fetched in kb2fetch dictionary of fetch2scope4xi.py
ξ (6b) check: path2read4xi # path for input source programs
ξ (6c) check: path2write4xi # path for output source programs
ξ (6d) in command mode >go2studio
ξ (6e) >fetch2scope4xi
ξ »apu3image4xi.py
ξ »apu3image4xi5test.py

(7) Generate Dragon modules of Programs for APU to Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or APU has so many changes that a new dragon module is easier to make
ξ (7a) »dragonize2scope4xi.py
ξ (7b) kb2dragonize["apu3image4xi.py"] = "dragon3image4xi.py"
ξ (7c) kb2dragonize["apu3image4xi5test.py"] = "dragon3image4xi5test.py"
ξ (7d) in command mode >dragonize2scope4xi
ξ (7e) »dragon3image4xi.py
ξ (7f) »dragon3image4xi5test.py
ξ (7g) do not delete trace of APU - it has been created in the way that will be dragonize ok

(8) Generate from Dragon Program module modules to {BPU,CPU ... ZPU} - mandatory - {APU} must be skipped
ξ ** warning ** do NOT generate for your reference processing unit, in this case APU processing unit is skipped!
ξ you need one good and real processing unit as master and base for other processing unit
ξ although system could generate source code also to your reference processing unit, do NOT let it do it!
ξ if something goes wrong you'll need the source files of your reference processing unit!
ξ generation may tailor code based on each processing unit capabilities and features!
ξ (8a) »generate2kernel4scope.py
ξ (8b) edited generator for program using kernel generator as base
ξ (8c) »print4xi.py
ξ (8d) updated trace for Studio4xi
ξ (8e) »pickle2g4xi.py
ξ (8f) updated pickling
ξ (8g) »actor2g4xi.py
ξ (8h) updated actors

(9) Generate
ξ (9a) »generate2kernel4scope.py
ξ kb2tailor <-- update (if necessary) to generate apu3image4xi.py .. apu3image4xi.py
ξ (9a) »dragon3image4xi.py
ξ (9b) »version4xi.py
ξ (9c) update ActKB4scope dictionary with new module
ξ (9d) ActKB4scope ['z'] ['generate2kernel4scope'] = 'ACK' # FIRST TO GENERATE BY SETTING TO 'ACK'!
ξ (9e) version4xi.py defines which processing unit kernel is to be developed - you generate for one at a time
ξ (9f) replace used output ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib <-- ROOT2TEMP4SCOPE:out\lib (empty)
ξ (9g) either >generate2kernel4scope
ξ (9g) or >python generate2kernel4scope.py > ROOT2JOB4SCOPE:\04711\studio4xi\cc\generate\out\txt\generate2kernel4scope.txt
ξ (9h) check ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\generate2kernel4scope.txt
ξ REMEMBER: version4xi.py ActKB4scope changes for each object and its tester!

(10) Compile one and generate to other processing units
ξ (10a) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\z\zpu3image4xi.py --> ROOT2SCOPE4XI:\041721\zap\lib\z\zpu3image4xi.py
ξ (10b) »zpu3image4xi.py
ξ (10c) compile it!
ξ (10d) ActKB4scope of version4xi.py <-- edit and run for each processing unit - ONE at a time NOT many at the same time!
ξ (10e) take backups from your current Scope4Xi BEFORE proceeding!
ξ (10f) check output programs BEFORE copying them in ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out <-- 25 files in 26 folders!
ξ (10g) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\
ξ (10h) compile all by running all2c - if there are errors you most propably tried to generate several programs in one run!
ξ DONE - you have generated kernel object modules to processing units {BPU ... GPU ...ZPU} and NOT for {APU}

(11) Generate Commandqueue4Xi5test modules as above
ξ (11a) »generate2kernel4scope.py
ξ define test module: kb2tailor ['b'] ['module'] = 'bpu3image4xi5test.py' ... kb2tailor ['z'] ['module'] = 'zpu3image4xi5test.py'
ξ (11b) »version4xi.py
ξ as above ActKB4scope ['b'] ['generate2kernel4scope'] = 'ACK' ... ActKB4scope ['z'] ['generate2kernel4scope'] = 'ACK' one at a time

(14) Copy generated Program modules to Scope4xi
ξ (14a) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\

(15) Update batch files - once
ξ only once - skipped in this version

(16) Compile and test Program modules all processing units
ξ (16a) >all2c in command mode of Scope4xi
ξ (16b) ROOT2SCOPE4XI:\041721\zap\work\txt <-- see that all are updated, check some if any there are FAILED messages
ξ (16c) ROOT2SCOPE4XI:\041721\zap\web\xml <-- see that all are updated and browser some

(17) DONE
ξ backup ROOT2SCOPE4XI:\041721
ξ backup ROOT2JOB4SCOPE:\041721

1) APU reference processing unit ones created with physical processing unit
ξ »apu3image4xi.py
ξ »apu3image4xi5test.py

2) DRAGON processing unit ones created from APU and used to automatically by software to generate software for {BPU ... GPU ... ZPU}
ξ »dragon3image4xi.py
ξ »dragon3image4xi5test.py

3) Commandqueue objects for processing units {BPU ... GPU ... ZPU}
ξ »bpu3image4xi.py
ξ »bpu3image4xi5test.py
ξ BPU generated ones
...
ξ »gpu3image4xi.py
ξ »gpu3image4xi5test.py
ξ GPU generated ones
...
ξ »zpu3image4xi.py
ξ »zpu3image4xi5test.py
ξ ZPU generated ones

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Context

Context Objects for {BPU ... GPU ... ZPU}

DRAGON
ξ base processing unit used to automatically generate context objects to other processing units
ξ »dragon2context4xi.py

(1) Find Model - optional
ξ this step is needed when another working source file is used as a model to create source file to handle context objects
ξ »apu2sampler4xi.py
ξ »apu2sampler4xi5test.py
ξ used as base for context objects

(2) Edit Programs - optional
ξ create source files for the processing unit APU
ξ »apu2context4xi.py

ξ edited Public API comparing to the OpenCL specificatio and removed extra functions and methods
ξ set2context4apu, set2contextcallback4apu and trace2context4apu defined as in any Scope4Xi modules (not in OpenCL specs!)

(3) Set Trace for Programs - once
ξ »print4xi.py
ξ both class and function to all devices {APU ... ZPU} and virtual device {xi}
ξ set debug = True if print4xi.py denies trace

(4) Update Pickle Modules - once
ξ »pickle2a4xi.py
...
ξ »pickle2d4xi.py
ξ special DRAGON processing unit!
...
ξ »pickle2z4xi.py

(5) Test Program for APU (reference processing unit)
ξ processing unit could be any, APU was selected here
ξ »apu2context4xi.py

(6) Fetch Programs for APU in Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or there are others reasons to update dragon program
ξ »fetch2scope4xi.py
ξ »version4xi.py
ξ (6a) define apu2context4xi.py and apu2context4xi5test.py as programs to be fetched in kb2fetch dictionary of fetch2scope4xi.py
ξ (6b) check: path2read4xi # path for input source programs
ξ (6c) check: path2write4xi # path for output source programs
ξ (6d) in command mode >go2studio
ξ (6e) >fetch2scope4xi
ξ »apu2context4xi.py

(7) Generate Dragon modules of Programs for APU to Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or APU has so many changes that a new dragon module is easier to make
ξ (7a) »dragonize2scope4xi.py
ξ (7b) kb2dragonize["apu2context4xi.py"] = "dragon2context4xi.py"
ξ (7c) kb2dragonize["apu2context4xi5test.py"] = "dragon2context4xi5test.py"
ξ (7d) in command mode >dragonize2scope4xi
ξ (7e) »dragon2context4xi.py
ξ (7g) do not delete trace of APU - it has been created in the way that will be dragonize ok

(8) Generate from Dragon Program module modules to {BPU,CPU ... ZPU} - mandatory - {APU} must be skipped
ξ ** warning ** do NOT generate for your reference processing unit, in this case APU processing unit is skipped!
ξ you need one good and real processing unit as master and base for other processing unit
ξ although system could generate source code also to your reference processing unit, do NOT let it do it!
ξ if something goes wrong you'll need the source files of your reference processing unit!
ξ generation may tailor code based on each processing unit capabilities and features!
ξ (8a) »generate2context4scope.py
ξ (8b) edited generator for program using sampler generator as base
ξ (8c) »print4xi.py
ξ (8d) updated trace for Studio4xi
ξ (8e) »pickle2g4xi.py
ξ (8f) updated pickling
ξ (8g) »actor2g4xi.py
ξ (8h) updated actors

(9) Generate
ξ (9a) »generate2context4scope.py
ξ kb2tailor <-- update (if necessary) to generate apu2context4xi.py .. apu2context4xi.py
ξ (9a) »dragon2context4xi.py
ξ (9b) »version4xi.py
ξ (9c) update ActKB4scope dictionary with new module
ξ (9d) ActKB4scope ['z'] ['generate2context4scope'] = 'ACK' # FIRST TO GENERATE BY SETTING TO 'ACK'!
ξ (9e) version4xi.py defines which processing unit context is to be developed - you generate for one at a time
ξ (9f) replace used output ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib <-- ROOT2TEMP4SCOPE:out\lib (empty)
ξ (9g) either >generate2context4scope
ξ (9g) or >python generate2context4scope.py > ROOT2JOB4SCOPE:\04711\studio4xi\cc\generate\out\txt\generate2context4scope.txt
ξ (9h) check ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\generate2context4scope.txt
ξ REMEMBER: version4xi.py ActKB4scope changes for each object and its tester!

(10) Compile one and generate to other processing units
ξ (10a) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\z\zpu2context4xi.py --> ROOT2SCOPE4XI:\041721\zap\lib\z\zpu2context4xi.py
ξ (10b) »zpu2context4xi.py
ξ (10c) compile it!
ξ (10d) ActKB4scope of version4xi.py <-- edit and run for each processing unit - ONE at a time NOT many at the same time!
ξ (10e) take backups from your current Scope4Xi BEFORE proceeding!
ξ (10f) check output programs BEFORE copying them in ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out <-- 25 files in 26 folders!
ξ (10g) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\
ξ (10h) compile all by running all2c - if there are errors you most propably tried to generate several programs in one run!
ξ DONE - you have generated context object modules to processing units {BPU ... GPU ...ZPU} and NOT for {APU}

(11) Generate Context4Xi5test module for ZPU
ξ (11a) skipped because other context objects are being used and tested by other objects

(12) Generate Context4Xi5test module for other devices {BPU ... YPU}
ξ (12a) skipped because other context objects are being used and tested by other objects

(14) Copy generated Program modules to Scope4xi
ξ (14a) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\

(15) Update batch files - once
ξ only once - skipped in this version

(16) Compile and test Program modules all processing units
ξ (16a) >all2c in command mode of Scope4xi
ξ (16b) ROOT2SCOPE4XI:\041721\zap\work\txt <-- see that all are updated, check some if any there are FAILED messages
ξ (16c) ROOT2SCOPE4XI:\041721\zap\web\xml <-- see that all are updated and browser some

(17) DONE
ξ backup ROOT2SCOPE4XI:\041721
ξ backup ROOT2JOB4SCOPE:\041721

1) APU reference processing unit ones created with physical processing unit
ξ »apu2context4xi.py

2) DRAGON processing unit ones created from APU and used to automatically by software to generate software for {BPU ... GPU ... ZPU}
ξ »dragon2context4xi.py

3) Context objects for processing units {BPU ... GPU ... ZPU}
ξ »bpu2context4xi.py
ξ BPU generated ones
...
ξ »gpu2context4xi.py
ξ GPU generated ones
...
ξ »zpu2context4xi.py
ξ ZPU generated ones

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ State Machine or Thread

State Machine or Thread

ξ »apu3image4xi.py
ξ »apu3image4xi5test.py
ξ »apu2image4xi.py
ξ »apu2image4xi5test.py

Solution selected:
ξ test programs call manoueuvre functions which change their state either to communicate via pipe or queue
ξ + queue and pipe are being processed only when needed
ξ - user has to call i.e to kick manoeuvre function which must be coded as state machine

Option embedded:
ξ thread i.e. dummy process could be activated with manoeuvre function as target function
ξ + thread could work simultaneously, sending and receiving via pipe without kicking, put and get via queue without kicking
ξ - unresolved how caller could give time to others if it wants to wait manoueuvre function
ξ - slower and might waste computer resources and more risky because Queue4Xi queue mechanism in multiprocessing uses named pipes and may not work at the same time with Pipe4Xi

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Sampler Objects for {BPU ... GPU ... ZPU}

Sampler Objects for {BPU ... GPU ... ZPU}

DRAGON
ξ base processing unit used to automatically generate sampler objects to other processing units
ξ »dragon2sampler4xi.py

(1) Find Model - optional
ξ this step is needed when another working source file is used as a model to create source file to handle sampler objects
ξ »apu2sampler4xi.py
ξ »apu2sampler4xi5test.py
ξ used as base for sampler objects

(2) Edit Programs - optional
ξ create source files for the processing unit APU
ξ »apu2sampler4xi.py
ξ »apu2sampler4xi5test.py
ξ edited Public API comparing to the OpenCL specificatio and removed extra functions and methods
ξ set2sampler4apu, set2samplercallback4apu and trace2sampler4apu defined as in any Scope4Xi modules (not in OpenCL specs!)

(3) Set Trace for Programs - once
ξ »print4xi.py
ξ both class and function to all samplers {APU ... ZPU} and virtual sampler {xi}
ξ set debug = True if print4xi.py denies trace

(4) Update Pickle Modules - once
ξ »pickle2a4xi.py
...
ξ »pickle2d4xi.py
ξ special DRAGON processing unit!
...
ξ »pickle2z4xi.py

(5) Test Program for APU (reference processing unit)
ξ processing unit could be any, APU was selected here
ξ »apu2sampler4xi.py
ξ »apu2sampler4xi5test.py
ξ »apu2sampler4xi5test.txt
ξ »ace-apu2sampler4xi5test
ξ »reason-apu2sampler4xi5test
ξ »sense-apu2sampler4xi5test

(6) Fetch Programs for APU in Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or there are others reasons to update dragon program
ξ »fetch2scope4xi.py
ξ »version4xi.py
ξ (6a) define apu2sampler4xi.py and apu2sampler4xi5test.py as programs to be fetched in kb2fetch dictionary of fetch2scope4xi.py
ξ (6b) check: path2read4xi # path for input source programs
ξ (6c) check: path2write4xi # path for output source programs
ξ (6d) in command mode >go2studio
ξ (6e) >fetch2scope4xi
ξ »apu2sampler4xi.py
ξ »apu2sampler4xi5test.py

(7) Generate Dragon modules of Programs for APU to Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or APU has so many changes that a new dragon module is easier to make
ξ (7a) »dragonize2scope4xi.py
ξ (7b) kb2dragonize["apu2sampler4xi.py"] = "dragon2sampler4xi.py"
ξ (7c) kb2dragonize["apu2sampler4xi5test.py"] = "dragon2sampler4xi5test.py"
ξ (7d) in command mode >dragonize2scope4xi
ξ (7e) »dragon2sampler4xi.py
ξ (7f) »dragon2sampler4xi5test.py
ξ (7g) do not delete trace of APU - it has been created in the way that will be dragonize ok

(8) Generate from Dragon Program module modules to {BPU,CPU ... ZPU} - mandatory - {APU} must be skipped
ξ ** warning ** do NOT generate for your reference processing unit, in this case APU processing unit is skipped!
ξ you need one good and real processing unit as master and base for other processing unit
ξ although system could generate source code also to your reference processing unit, do NOT let it do it!
ξ if something goes wrong you'll need the source files of your reference processing unit!
ξ generation may tailor code based on each processing unit capabilities and features!
ξ (8a) »generate2sampler4scope.py
ξ (8b) edited generator for program using sampler generator as base
ξ (8c) »print4xi.py
ξ (8d) updated trace for Studio4xi
ξ (8e) »pickle2g4xi.py
ξ (8f) updated pickling
ξ (8g) »actor2g4xi.py
ξ (8h) updated actors

(9) Generate
ξ (9a) »generate2sampler4scope.py
ξ kb2tailor <-- update (if necessary) to generate apu2sampler4xi.py .. apu2sampler4xi.py
ξ (9a) »dragon2sampler4xi.py
ξ (9b) »version4xi.py
ξ (9c) update ActKB4scope dictionary with new module
ξ (9d) ActKB4scope ['z'] ['generate2sampler4scope'] = 'ACK' # FIRST TO GENERATE BY SETTING TO 'ACK'!
ξ (9e) version4xi.py defines which processing unit sampler is to be developed - you generate for one at a time
ξ (9f) replace used output ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib <-- ROOT2TEMP4SCOPE:out\lib (empty)
ξ (9g) either >generate2sampler4scope
ξ (9g) or >python generate2sampler4scope.py > ROOT2JOB4SCOPE:\04711\studio4xi\cc\generate\out\txt\generate2sampler4scope.txt
ξ (9h) check ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\generate2sampler4scope.txt
ξ REMEMBER: version4xi.py ActKB4scope changes for each object and its tester!

(10) Compile one and generate to other processing units
ξ (10a) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\z\zpu2sampler4xi.py --> ROOT2SCOPE4XI:\041721\zap\lib\z\zpu2sampler4xi.py
ξ (10b) »zpu2sampler4xi.py
ξ (10c) compile it!
ξ (10d) ActKB4scope of version4xi.py <-- edit and run for each processing unit - ONE at a time NOT many at the same time!
ξ (10e) take backups from your current Scope4Xi BEFORE proceeding!
ξ (10f) check output programs BEFORE copying them in ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out <-- 25 files in 26 folders!
ξ (10g) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\
ξ (10h) compile all by running all2c - if there are errors you most propably tried to generate several programs in one run!
ξ DONE - you have generated sampler object modules to processing units {BPU ... GPU ...ZPU} and NOT for {APU}

(11) Generate Commandqueue4Xi5test modules as above
ξ (11a) »generate2sampler4scope.py
ξ define test module: kb2tailor ['b'] ['module'] = 'bpu2sampler4xi5test.py' ... kb2tailor ['z'] ['module'] = 'zpu2sampler4xi5test.py'
ξ (11b) »version4xi.py
ξ as above ActKB4scope ['b'] ['generate2sampler4scope'] = 'ACK' ... ActKB4scope ['z'] ['generate2sampler4scope'] = 'ACK' one at a time

(14) Copy generated Program modules to Scope4xi
ξ (14a) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\

(15) Update batch files - once
ξ only once - skipped in this version

(16) Compile and test Program modules all processing units
ξ (16a) >all2c in command mode of Scope4xi
ξ (16b) ROOT2SCOPE4XI:\041721\zap\work\txt <-- see that all are updated, check some if any there are FAILED messages
ξ (16c) ROOT2SCOPE4XI:\041721\zap\web\xml <-- see that all are updated and browser some

(17) DONE
ξ backup ROOT2SCOPE4XI:\041721
ξ backup ROOT2JOB4SCOPE:\041721

1) APU reference processing unit ones created with physical processing unit
ξ »apu2sampler4xi.py
ξ »apu2sampler4xi5test.py

2) DRAGON processing unit ones created from APU and used to automatically by software to generate software for {BPU ... GPU ... ZPU}
ξ »dragon2sampler4xi.py
ξ »dragon2sampler4xi5test.py

3) Commandqueue objects for processing units {BPU ... GPU ... ZPU}
ξ »bpu2sampler4xi.py
ξ »bpu2sampler4xi5test.py
ξ BPU generated ones
...
ξ »gpu2sampler4xi.py
ξ »gpu2sampler4xi5test.py
ξ GPU generated ones
...
ξ »zpu2sampler4xi.py
ξ »zpu2sampler4xi5test.py
ξ ZPU generated ones

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Actors

Actors

ξ »actor2a4xi.py
ξ to-be-done all scope4xi functions and classed to all actor2a4xi.py ... actor2z4xi.py modules
ξ »print4xi.py
ξ actors and trace must matchas well as »Picklers

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Picklers

Picklers

ξ »pickle2a4xi.py
ξ to-be-done all scope4xi functions and classed to all pickle2a4xi.py ... pickle2z4xi.py modules
ξ »print4xi.py
ξ picklers and trace must matchas well as »Actors

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Program Objects for {BPU ... GPU ... ZPU}

Program Objects for {BPU ... GPU ... ZPU}

DRAGON
ξ base processing unit used to automatically generate program objects to other processing units
ξ »dragon2program4xi.py

(1) Find Model - optional
ξ this step is needed when another working source file is used as a model to create source file to handle program objects
ξ »apu2sampler4xi.py
ξ »apu2sampler4xi5test.py
ξ used as base for program objects

(2) Edit Programs - optional
ξ create source files for the processing unit APU
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ edited Public API comparing to the OpenCL specificatio and removed extra functions and methods
ξ set2program4apu, set2programcallback4apu and trace2program4apu defined as in any Scope4Xi modules (not in OpenCL specs!)

(3) Set Trace for Programs - once
ξ »print4xi.py
ξ both class and function to all devices {APU ... ZPU} and virtual device {xi}
ξ set debug = True if print4xi.py denies trace

(4) Update Pickle Modules - once
ξ »pickle2a4xi.py
...
ξ »pickle2d4xi.py
ξ special DRAGON processing unit!
...
ξ »pickle2z4xi.py

(5) Test Program for APU (reference processing unit)
ξ processing unit could be any, APU was selected here
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ »apu2program4xi5test.txt
ξ »ace-apu2program4xi5test
ξ »reason-apu2program4xi5test
ξ »sense-apu2program4xi5test

(6) Fetch Programs for APU in Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or there are others reasons to update dragon program
ξ »fetch2scope4xi.py
ξ »version4xi.py
ξ (6a) define apu2program4xi.py and apu2program4xi5test.py as programs to be fetched in kb2fetch dictionary of fetch2scope4xi.py
ξ (6b) check: path2read4xi # path for input source programs
ξ (6c) check: path2write4xi # path for output source programs
ξ (6d) in command mode >go2studio
ξ (6e) >fetch2scope4xi
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py

(7) Generate Dragon modules of Programs for APU to Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or APU has so many changes that a new dragon module is easier to make
ξ (7a) »dragonize2scope4xi.py
ξ (7b) kb2dragonize["apu2program4xi.py"] = "dragon2program4xi.py"
ξ (7c) kb2dragonize["apu2program4xi5test.py"] = "dragon2program4xi5test.py"
ξ (7d) in command mode >dragonize2scope4xi
ξ (7e) »dragon2program4xi.py
ξ (7f) »dragon2program4xi5test.py
ξ (7g) do not delete trace of APU - it has been created in the way that will be dragonize ok

(8) Generate from Dragon Program module modules to {BPU,CPU ... ZPU} - mandatory - {APU} must be skipped
ξ ** warning ** do NOT generate for your reference processing unit, in this case APU processing unit is skipped!
ξ you need one good and real processing unit as master and base for other processing unit
ξ although system could generate source code also to your reference processing unit, do NOT let it do it!
ξ if something goes wrong you'll need the source files of your reference processing unit!
ξ generation may tailor code based on each processing unit capabilities and features!
ξ (8a) »generate2program4scope.py
ξ (8b) edited generator for program using sampler generator as base
ξ (8c) »print4xi.py
ξ (8d) updated trace for Studio4xi
ξ (8e) »pickle2g4xi.py
ξ (8f) updated pickling
ξ (8g) »actor2g4xi.py
ξ (8h) updated actors

(9) Generate
ξ (9a) »generate2program4scope.py
ξ kb2tailor <-- update (if necessary) to generate apu2program4xi.py .. apu2program4xi.py
ξ (9a) »dragon2program4xi.py
ξ (9b) »version4xi.py
ξ (9c) update ActKB4scope dictionary with new module
ξ (9d) ActKB4scope ['z'] ['generate2program4scope'] = 'ACK' # FIRST TO GENERATE BY SETTING TO 'ACK'!
ξ (9e) version4xi.py defines which processing unit program is to be developed - you generate for one at a time
ξ (9f) replace used output ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib <-- ROOT2TEMP4SCOPE:out\lib (empty)
ξ (9g) either >generate2program4scope
ξ (9g) or >python generate2program4scope.py > ROOT2JOB4SCOPE:\04711\studio4xi\cc\generate\out\txt\generate2program4scope.txt
ξ (9h) check ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\generate2program4scope.txt

(10) Compile one and generate to other processing units
ξ (10a) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\z\zpu2program4xi.py --> ROOT2SCOPE4XI:\041721\zap\lib\z\zpu2program4xi.py
ξ (10b) »zpu2program4xi.py
ξ (10c) compile it!
ξ (10d) ActKB4scope of version4xi.py <-- edit and run for each processing unit - ONE at a time NOT many at the same time!
ξ (10e) take backups from your current Scope4Xi BEFORE proceeding!
ξ (10f) check output programs BEFORE copying them!
ξ (10g) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\
ξ (10h) compile all by running all2c - if there are errors you most propably tried to generate several programs in one run!
ξ DONE - you have generated program object modules to processing units {BPU ... GPU ...ZPU} and NOT for {APU}

(11) Generate Program4Xi5test module for ZPU
ξ (11a) take backup
ξ (11b) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib <-- delete
ξ (11c) ROOT2TEMP4SCOPE:out\lib --> ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib
ξ (11d) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\in\lib\dragon <-- ROOT2SCOPE4XI:\041721\zap\lib\dragon\dragon2program4xi5test.py
ξ (11f) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\in\lib\dragon <-- delete other programs if any from previous runs
ξ (11f) »generate2program4scope.py
ξ (11g) edit to handle dragon2program4xi5test <-- change kb2tailor otherwise it generates new modules with wrong names!
ξ (11h) ActKB4scope ['z'] ['generate2program4scope'] = 'ACK' <--> check »version4xi.py
ξ (11i) >generate2program4scope
ξ (11j) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\z <-- watch
ξ (11k) »zpu2program4xi5test.py
ξ (11l) generated test program program for ZPU
ξ (11m) ROOT2SCOPE4XI:\041721\zap\lib\z\zpu2program4xi5test.py <-- ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\z\zpu2program4xi5test.py
ξ (11o) >go2scope
ξ (11p) >z2c
ξ (11q) »zpu2program4xi5test.txt
ξ (11r) test output: find FAILED messages, walk through finding OF ZPU2PROGRAM4XI5TEST lines
ξ (11s) »ace-zpu2program4xi5test.xml
ξ (11t) »reason-zpu2program4xi5test.xml
ξ (11u) »sense-zpu2program4xi5test.xml
ξ (11v) checked that XML files were generated for program of ZPU
ξ DONE - you have verified with ZPU processing unit

(12) Generate Program test modules for other devices {BPU ... YPU}
ξ (12a) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out <-- 25 files in 26 folder (APU processing unit folder /a skipped)

(14) Copy generated Program modules to Scope4xi
ξ (14a) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\

(15) Update batch files
ξ only once - skipped in this version

(16) Compile and test Program modules all processing units
ξ (16a) >all2c in command mode of Scope4xi
ξ (16b) ROOT2SCOPE4XI:\041721\zap\work\txt <-- see that all are updated, check some if any there are FAILED messages
ξ (16c) ROOT2SCOPE4XI:\041721\zap\web\xml <-- see that all are updated and browser some

(17) DONE
ξ backup ROOT2SCOPE4XI:\041721
ξ backup ROOT2JOB4SCOPE:\041721

1) APU reference processing unit ones created with physical processing unit
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py

2) DRAGON processing unit ones created from APU and used to automatically by software to generate software for {BPU ... GPU ... ZPU}
ξ »dragon2program4xi.py
ξ »dragon2program4xi5test.py

3) Program objects for processing units {BPU ... GPU ... ZPU}
ξ »bpu2program4xi.py
ξ »bpu2program4xi5test.py
ξ BPU generated ones
...
ξ »gpu2program4xi.py
ξ »gpu2program4xi5test.py
ξ GPU generated ones
...
ξ »zpu2program4xi.py
ξ »zpu2program4xi5test.py
ξ ZPU generated ones

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Test Modules

APU Test Modules

ξ »apu3image4xi5test.py
ξ »apu2sampler4xi5test.py
ξ »apu2image4xi5test.py
ξ »apu2event4xi5test.py
ξ »apu2commandqueue4xi5test.py
ξ »apu2program4xi5test.py

Notes
ξ in the beginning tests were not designed for individual processing units but only for virtual device xi
ξ once all OpenCL modules have been created, use automatic software generation to generate tests to APU ... ZPU!

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Special cases in tracing

Special cases in tracing

ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ you have to perform tailor2trace4program(t2xi) again if the target function of activated process resets trace!
ξ activated process creates its own XML files
ξ even if you tailor the trace again, the existing trace stays ok and xml files are built ok!

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Kernel Objects Objects for {BPU ... GPU ... ZPU}

Kernel Objects for {BPU ... GPU ... ZPU}

DRAGON
ξ base processing unit used to automatically generate kernel objects to other processing units
ξ »dragon2kernel4xi.py

(1) Find Model - optional
ξ this step is needed when another working source file is used as a model to create source file to handle kernel objects
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ used as base for kernel objects

(2) Edit Programs - optional
ξ create source files for the processing unit APU
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ edited Public API comparing to the OpenCL specificatio and removed extra functions and methods
ξ set2kernel4apu, set2kernelcallback4apu and trace2kernel4apu defined as in any Scope4Xi modules (not in OpenCL specs!)

(3) Set Trace for Programs - once
ξ »print4xi.py
ξ both class and function to all kernels {APU ... ZPU} and virtual kernel {xi}
ξ set debug = True if print4xi.py denies trace

(4) Update Pickle Modules - once
ξ »pickle2a4xi.py
...
ξ »pickle2d4xi.py
ξ special DRAGON processing unit!
...
ξ »pickle2z4xi.py

(5) Test Program for APU (reference processing unit)
ξ processing unit could be any, APU was selected here
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ »apu2kernel4xi5test.txt
ξ »ace-apu2kernel4xi5test
ξ »reason-apu2kernel4xi5test
ξ »sense-apu2kernel4xi5test

(6) Fetch Programs for APU in Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or there are others reasons to update dragon program
ξ »fetch2scope4xi.py
ξ »version4xi.py
ξ (6a) define apu2kernel4xi.py and apu2kernel4xi5test.py as programs to be fetched in kb2fetch dictionary of fetch2scope4xi.py
ξ (6b) check: path2read4xi # path for input source programs
ξ (6c) check: path2write4xi # path for output source programs
ξ (6d) in command mode >go2studio
ξ (6e) >fetch2scope4xi
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py

(7) Generate Dragon modules of Programs for APU to Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or APU has so many changes that a new dragon module is easier to make
ξ (7a) »dragonize2scope4xi.py
ξ (7b) kb2dragonize["apu2kernel4xi.py"] = "dragon2kernel4xi.py"
ξ (7c) kb2dragonize["apu2kernel4xi5test.py"] = "dragon2kernel4xi5test.py"
ξ (7d) in command mode >dragonize2scope4xi
ξ (7e) »dragon2kernel4xi.py
ξ (7f) »dragon2kernel4xi5test.py
ξ (7g) do not delete trace of APU - it has been created in the way that will be dragonize ok

(8) Generate from Dragon Program module modules to {BPU,CPU ... ZPU} - mandatory - {APU} must be skipped
ξ ** warning ** do NOT generate for your reference processing unit, in this case APU processing unit is skipped!
ξ you need one good and real processing unit as master and base for other processing unit
ξ although system could generate source code also to your reference processing unit, do NOT let it do it!
ξ if something goes wrong you'll need the source files of your reference processing unit!
ξ generation may tailor code based on each processing unit capabilities and features!
ξ (8a) »generate2kernel4scope.py
ξ (8b) edited generator for program using kernel generator as base
ξ (8c) »print4xi.py
ξ (8d) updated trace for Studio4xi
ξ (8e) »pickle2g4xi.py
ξ (8f) updated pickling
ξ (8g) »actor2g4xi.py
ξ (8h) updated actors

(9) Generate
ξ (9a) »generate2kernel4scope.py
ξ kb2tailor <-- update (if necessary) to generate apu2kernel4xi.py .. apu2kernel4xi.py
ξ (9a) »dragon2kernel4xi.py
ξ (9b) »version4xi.py
ξ (9c) update ActKB4scope dictionary with new module
ξ (9d) ActKB4scope ['z'] ['generate2kernel4scope'] = 'ACK' # FIRST TO GENERATE BY SETTING TO 'ACK'!
ξ (9e) version4xi.py defines which processing unit kernel is to be developed - you generate for one at a time
ξ (9f) replace used output ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib <-- ROOT2TEMP4SCOPE:out\lib (empty)
ξ (9g) either >generate2kernel4scope
ξ (9g) or >python generate2kernel4scope.py > ROOT2JOB4SCOPE:\04711\studio4xi\cc\generate\out\txt\generate2kernel4scope.txt
ξ (9h) check ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\generate2kernel4scope.txt
ξ REMEMBER: version4xi.py ActKB4scope changes for each object and its tester!

(10) Compile one and generate to other processing units
ξ (10a) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\z\zpu2kernel4xi.py --> ROOT2SCOPE4XI:\041721\zap\lib\z\zpu2kernel4xi.py
ξ (10b) »zpu2kernel4xi.py
ξ (10c) compile it!
ξ (10d) ActKB4scope of version4xi.py <-- edit and run for each processing unit - ONE at a time NOT many at the same time!
ξ (10e) take backups from your current Scope4Xi BEFORE proceeding!
ξ (10f) check output programs BEFORE copying them in ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out <-- 25 files in 26 folders!
ξ (10g) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\
ξ (10h) compile all by running all2c - if there are errors you most propably tried to generate several programs in one run!
ξ DONE - you have generated kernel object modules to processing units {BPU ... GPU ...ZPU} and NOT for {APU}

(11) Generate Commandqueue4Xi5test modules as above
ξ (11a) »generate2kernel4scope.py
ξ define test module: kb2tailor ['b'] ['module'] = 'bpu2kernel4xi5test.py' ... kb2tailor ['z'] ['module'] = 'zpu2kernel4xi5test.py'
ξ (11b) »version4xi.py
ξ as above ActKB4scope ['b'] ['generate2kernel4scope'] = 'ACK' ... ActKB4scope ['z'] ['generate2kernel4scope'] = 'ACK' one at a time

(14) Copy generated Program modules to Scope4xi
ξ (14a) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\

(15) Update batch files - once
ξ only once - skipped in this version

(16) Compile and test Program modules all processing units
ξ (16a) >all2c in command mode of Scope4xi
ξ (16b) ROOT2SCOPE4XI:\041721\zap\work\txt <-- see that all are updated, check some if any there are FAILED messages
ξ (16c) ROOT2SCOPE4XI:\041721\zap\web\xml <-- see that all are updated and browser some

(17) DONE
ξ backup ROOT2SCOPE4XI:\041721
ξ backup ROOT2JOB4SCOPE:\041721

1) APU reference processing unit ones created with physical processing unit
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py

2) DRAGON processing unit ones created from APU and used to automatically by software to generate software for {BPU ... GPU ... ZPU}
ξ »dragon2kernel4xi.py
ξ »dragon2kernel4xi5test.py

3) Commandqueue objects for processing units {BPU ... GPU ... ZPU}
ξ »bpu2kernel4xi.py
ξ »bpu2kernel4xi5test.py
ξ BPU generated ones
...
ξ »gpu2kernel4xi.py
ξ »gpu2kernel4xi5test.py
ξ GPU generated ones
...
ξ »zpu2kernel4xi.py
ξ »zpu2kernel4xi5test.py
ξ ZPU generated ones

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Tracing Xi Device Modules

Tracing Xi Device Modules

ξ Xi = {APU,BPU,CPU ... ZPU} »API
ξ when you test or use XI device you can use all twenty six(26) processing units
ξ also, you can limit trace and make testing easier and faster by selecting subset such as {APU,ZPU}:
ξ ace highly parallel dragonized »API!

Example

# ---------------------------------------------------------------------------------------------
# Settings to tailor trace only for selected processing unit and xi
# ---------------------------------------------------------------------------------------------
KB4Tailoring = {
'APU2Sampler4Xi': 'NACK4XI', # APU <-- processing unit #1
'create2sampler4apu': 'NACK4XI',
# 'get2samplerinfo4apu': 'NACK4XI',
# 'retain2sampler4apu': 'NACK4XI',
# 'release2sampler4apu': 'NACK4XI',
# 'trace2sampler4apu': 'NACK4XI',
# 'set2samplercallback4apu': 'NACK4XI',
# 'set2sampler4apu': 'NACK4XI',
# 'ZPU2Sampler4Xi': 'NACK4XI', # ZPU <-- processing unit #2
# 'create2sampler4zpu': 'NACK4XI',
# 'get2samplerinfo4zpu': 'NACK4XI',
# 'retain2sampler4zpu': 'NACK4XI',
# 'release2sampler4zpu': 'NACK4XI',
# 'trace2sampler4zpu': 'NACK4XI',
# 'set2samplercallback4zpu': 'NACK4XI',
# 'set2sampler4zpu': 'NACK4XI',
'Sampler4Xi': 'NACK4XI', # XI <-- device
'create2sampler4xi': 'NACK4XI',
# 'get2samplerinfo4xi': 'NACK4XI',
# 'retain2sampler4xi': 'NACK4XI',
# 'release2sampler4xi': 'NACK4XI',
# 'trace2sampler4xi': 'NACK4XI',
# 'set2samplercallback4xi': 'NACK4XI',
# 'set2sampler4xi': 'NACK4XI'
}

ξ »sampler4xi.py
ξ »sampler4xi5test.py

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Command Queue Objects for {BPU ... GPU ... ZPU}

Command Queue Objects for {BPU ... GPU ... ZPU}

DRAGON
ξ base processing unit used to automatically generate commandqueue objects to other processing units
ξ »dragon2commandqueue4xi.py

(1) Find Model - optional
ξ this step is needed when another working source file is used as a model to create source file to handle commandqueue objects
ξ »apu2sampler4xi.py
ξ »apu2sampler4xi5test.py
ξ used as base for commandqueue objects

(2) Edit Programs - optional
ξ create source files for the processing unit APU
ξ »apu2commandqueue4xi.py
ξ »apu2commandqueue4xi5test.py
ξ edited Public API comparing to the OpenCL specificatio and removed extra functions and methods
ξ set2commandqueue4apu, set2commandqueuecallback4apu and trace2commandqueue4apu defined as in any Scope4Xi modules (not in OpenCL specs!)

(3) Set Trace for Programs - once
ξ »print4xi.py
ξ both class and function to all commandqueues {APU ... ZPU} and virtual commandqueue {xi}
ξ set debug = True if print4xi.py denies trace

(4) Update Pickle Modules - once
ξ »pickle2a4xi.py
...
ξ »pickle2d4xi.py
ξ special DRAGON processing unit!
...
ξ »pickle2z4xi.py

(5) Test Program for APU (reference processing unit)
ξ processing unit could be any, APU was selected here
ξ »apu2commandqueue4xi.py
ξ »apu2commandqueue4xi5test.py
ξ »apu2commandqueue4xi5test.txt
ξ »ace-apu2commandqueue4xi5test
ξ »reason-apu2commandqueue4xi5test
ξ »sense-apu2commandqueue4xi5test

(6) Fetch Programs for APU in Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or there are others reasons to update dragon program
ξ »fetch2scope4xi.py
ξ »version4xi.py
ξ (6a) define apu2commandqueue4xi.py and apu2commandqueue4xi5test.py as programs to be fetched in kb2fetch dictionary of fetch2scope4xi.py
ξ (6b) check: path2read4xi # path for input source programs
ξ (6c) check: path2write4xi # path for output source programs
ξ (6d) in command mode >go2studio
ξ (6e) >fetch2scope4xi
ξ »apu2commandqueue4xi.py
ξ »apu2commandqueue4xi5test.py

(7) Generate Dragon modules of Programs for APU to Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or APU has so many changes that a new dragon module is easier to make
ξ (7a) »dragonize2scope4xi.py
ξ (7b) kb2dragonize["apu2commandqueue4xi.py"] = "dragon2commandqueue4xi.py"
ξ (7c) kb2dragonize["apu2commandqueue4xi5test.py"] = "dragon2commandqueue4xi5test.py"
ξ (7d) in command mode >dragonize2scope4xi
ξ (7e) »dragon2commandqueue4xi.py
ξ (7f) »dragon2commandqueue4xi5test.py
ξ (7g) do not delete trace of APU - it has been created in the way that will be dragonize ok

(8) Generate from Dragon Program module modules to {BPU,CPU ... ZPU} - mandatory - {APU} must be skipped
ξ ** warning ** do NOT generate for your reference processing unit, in this case APU processing unit is skipped!
ξ you need one good and real processing unit as master and base for other processing unit
ξ although system could generate source code also to your reference processing unit, do NOT let it do it!
ξ if something goes wrong you'll need the source files of your reference processing unit!
ξ generation may tailor code based on each processing unit capabilities and features!
ξ (8a) »generate2commandqueue4scope.py
ξ (8b) edited generator for program using sampler generator as base
ξ (8c) »print4xi.py
ξ (8d) updated trace for Studio4xi
ξ (8e) »pickle2g4xi.py
ξ (8f) updated pickling
ξ (8g) »actor2g4xi.py
ξ (8h) updated actors

(9) Generate
ξ (9a) »generate2commandqueue4scope.py
ξ kb2tailor <-- update (if necessary) to generate apu2commandqueue4xi.py .. apu2commandqueue4xi.py
ξ (9a) »dragon2commandqueue4xi.py
ξ (9b) »version4xi.py
ξ (9c) update ActKB4scope dictionary with new module
ξ (9d) ActKB4scope ['z'] ['generate2commandqueue4scope'] = 'ACK' # FIRST TO GENERATE BY SETTING TO 'ACK'!
ξ (9e) version4xi.py defines which processing unit commandqueue is to be developed - you generate for one at a time
ξ (9f) replace used output ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib <-- ROOT2TEMP4SCOPE:out\lib (empty)
ξ (9g) either >generate2commandqueue4scope
ξ (9g) or >python generate2commandqueue4scope.py > ROOT2JOB4SCOPE:\04711\studio4xi\cc\generate\out\txt\generate2commandqueue4scope.txt
ξ (9h) check ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\generate2commandqueue4scope.txt
ξ REMEMBER: version4xi.py ActKB4scope changes for each object and its tester!

(10) Compile one and generate to other processing units
ξ (10a) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\z\zpu2commandqueue4xi.py --> ROOT2SCOPE4XI:\041721\zap\lib\z\zpu2commandqueue4xi.py
ξ (10b) »zpu2commandqueue4xi.py
ξ (10c) compile it!
ξ (10d) ActKB4scope of version4xi.py <-- edit and run for each processing unit - ONE at a time NOT many at the same time!
ξ (10e) take backups from your current Scope4Xi BEFORE proceeding!
ξ (10f) check output programs BEFORE copying them in ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out <-- 25 files in 26 folders!
ξ (10g) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\
ξ (10h) compile all by running all2c - if there are errors you most propably tried to generate several programs in one run!
ξ DONE - you have generated commandqueue object modules to processing units {BPU ... GPU ...ZPU} and NOT for {APU}

(11) Generate Commandqueue4Xi5test modules as above
ξ (11a) »generate2commandqueue4scope.py
ξ define test module: kb2tailor ['b'] ['module'] = 'bpu2commandqueue4xi5test.py' ... kb2tailor ['z'] ['module'] = 'zpu2commandqueue4xi5test.py'
ξ (11b) »version4xi.py
ξ as above ActKB4scope ['b'] ['generate2commandqueue4scope'] = 'ACK' ... ActKB4scope ['z'] ['generate2commandqueue4scope'] = 'ACK' one at a time

(14) Copy generated Program modules to Scope4xi
ξ (14a) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\

(15) Update batch files - once
ξ only once - skipped in this version

(16) Compile and test Program modules all processing units
ξ (16a) >all2c in command mode of Scope4xi
ξ (16b) ROOT2SCOPE4XI:\041721\zap\work\txt <-- see that all are updated, check some if any there are FAILED messages
ξ (16c) ROOT2SCOPE4XI:\041721\zap\web\xml <-- see that all are updated and browser some

(17) DONE
ξ backup ROOT2SCOPE4XI:\041721
ξ backup ROOT2JOB4SCOPE:\041721

1) APU reference processing unit ones created with physical processing unit
ξ »apu2commandqueue4xi.py
ξ »apu2commandqueue4xi5test.py

2) DRAGON processing unit ones created from APU and used to automatically by software to generate software for {BPU ... GPU ... ZPU}
ξ »dragon2commandqueue4xi.py
ξ »dragon2commandqueue4xi5test.py

3) Commandqueue objects for processing units {BPU ... GPU ... ZPU}
ξ »bpu2commandqueue4xi.py
ξ »bpu2commandqueue4xi5test.py
ξ BPU generated ones
...
ξ »gpu2commandqueue4xi.py
ξ »gpu2commandqueue4xi5test.py
ξ GPU generated ones
...
ξ »zpu2commandqueue4xi.py
ξ »zpu2commandqueue4xi5test.py
ξ ZPU generated ones

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Buffer Objects for {BPU ... GPU ... ZPU}

Buffer Objects for {BPU ... GPU ... ZPU}

DRAGON
ξ base processing unit used to automatically generate buffer objects to other processing units
ξ »dragon2buffer4xi.py

(1) Find Model - optional
ξ this step is needed when another working source file is used as a model to create source file to handle buffer objects
ξ »apu2sampler4xi.py
ξ »apu2sampler4xi5test.py
ξ used as base for buffer objects

(2) Edit Programs - optional
ξ create source files for the processing unit APU
ξ »apu2buffer4xi.py
ξ edited Public API comparing to the OpenCL specificatio and removed extra functions and methods
ξ set2buffer4apu, set2buffercallback4apu and trace2buffer4apu defined as in any Scope4Xi modules (not in OpenCL specs!)

(3) Set Trace for Programs - once
ξ »print4xi.py
ξ both class and function to all devices {APU ... ZPU} and virtual device {xi}
ξ set debug = True if print4xi.py denies trace

(4) Update Pickle Modules - once
ξ »pickle2a4xi.py
...
ξ »pickle2d4xi.py
ξ special DRAGON processing unit!
...
ξ »pickle2z4xi.py

(5) Test Program for APU (reference processing unit)
ξ processing unit could be any, APU was selected here
ξ »apu2buffer4xi.py

(6) Fetch Programs for APU in Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or there are others reasons to update dragon program
ξ »fetch2scope4xi.py
ξ »version4xi.py
ξ (6a) define apu2buffer4xi.py and apu2buffer4xi5test.py as programs to be fetched in kb2fetch dictionary of fetch2scope4xi.py
ξ (6b) check: path2read4xi # path for input source programs
ξ (6c) check: path2write4xi # path for output source programs
ξ (6d) in command mode >go2studio
ξ (6e) >fetch2scope4xi
ξ »apu2buffer4xi.py

(7) Generate Dragon modules of Programs for APU to Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or APU has so many changes that a new dragon module is easier to make
ξ (7a) »dragonize2scope4xi.py
ξ (7b) kb2dragonize["apu2buffer4xi.py"] = "dragon2buffer4xi.py"
ξ (7c) kb2dragonize["apu2buffer4xi5test.py"] = "dragon2buffer4xi5test.py"
ξ (7d) in command mode >dragonize2scope4xi
ξ (7e) »dragon2buffer4xi.py
ξ (7g) do not delete trace of APU - it has been created in the way that will be dragonize ok

(8) Generate from Dragon Program module modules to {BPU,CPU ... ZPU} - mandatory - {APU} must be skipped
ξ ** warning ** do NOT generate for your reference processing unit, in this case APU processing unit is skipped!
ξ you need one good and real processing unit as master and base for other processing unit
ξ although system could generate source code also to your reference processing unit, do NOT let it do it!
ξ if something goes wrong you'll need the source files of your reference processing unit!
ξ generation may tailor code based on each processing unit capabilities and features!
ξ (8a) »generate2buffer4scope.py
ξ (8b) edited generator for program using sampler generator as base
ξ (8c) »print4xi.py
ξ (8d) updated trace for Studio4xi
ξ (8e) »pickle2g4xi.py
ξ (8f) updated pickling
ξ (8g) »actor2g4xi.py
ξ (8h) updated actors

(9) Generate
ξ (9a) »generate2buffer4scope.py
ξ kb2tailor <-- update (if necessary) to generate apu2buffer4xi.py .. apu2buffer4xi.py
ξ (9a) »dragon2buffer4xi.py
ξ (9b) »version4xi.py
ξ (9c) update ActKB4scope dictionary with new module
ξ (9d) ActKB4scope ['z'] ['generate2buffer4scope'] = 'ACK' # FIRST TO GENERATE BY SETTING TO 'ACK'!
ξ (9e) version4xi.py defines which processing unit buffer is to be developed - you generate for one at a time
ξ (9f) replace used output ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib <-- ROOT2TEMP4SCOPE:out\lib (empty)
ξ (9g) either >generate2buffer4scope
ξ (9g) or >python generate2buffer4scope.py > ROOT2JOB4SCOPE:\04711\studio4xi\cc\generate\out\txt\generate2buffer4scope.txt
ξ (9h) check ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\generate2buffer4scope.txt
ξ REMEMBER: version4xi.py ActKB4scope changes for each object and its tester!

(10) Compile one and generate to other processing units
ξ (10a) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\z\zpu2buffer4xi.py --> ROOT2SCOPE4XI:\041721\zap\lib\z\zpu2buffer4xi.py
ξ (10b) »zpu2buffer4xi.py
ξ (10c) compile it!
ξ (10d) ActKB4scope of version4xi.py <-- edit and run for each processing unit - ONE at a time NOT many at the same time!
ξ (10e) take backups from your current Scope4Xi BEFORE proceeding!
ξ (10f) check output programs BEFORE copying them!
ξ (10g) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\
ξ (10h) compile all by running all2c - if there are errors you most propably tried to generate several programs in one run!
ξ DONE - you have generated program object modules to processing units {BPU ... GPU ...ZPU} and NOT for {APU}

(11) Generate Buffer4Xi5test module for ZPU
ξ (11a) skipped because other buffer objects are being used and tested by other objects

(12) Generate Buffer4Xi5test module for other devices {BPU ... YPU}
ξ (12a) skipped because other buffer objects are being used and tested by other objects

(14) Copy generated Program modules to Scope4xi
ξ (14a) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\

(15) Update batch files - once
ξ only once - skipped in this version

(16) Compile and test Program modules all processing units
ξ (16a) >all2c in command mode of Scope4xi
ξ (16b) ROOT2SCOPE4XI:\041721\zap\work\txt <-- see that all are updated, check some if any there are FAILED messages
ξ (16c) ROOT2SCOPE4XI:\041721\zap\web\xml <-- see that all are updated and browser some

(17) DONE
ξ backup ROOT2SCOPE4XI:\041721
ξ backup ROOT2JOB4SCOPE:\041721

1) APU reference processing unit ones created with physical processing unit
ξ »apu2buffer4xi.py

2) DRAGON processing unit ones created from APU and used to automatically by software to generate software for {BPU ... GPU ... ZPU}
ξ »dragon2buffer4xi.py

3) Buffer objects for processing units {BPU ... GPU ... ZPU}
ξ »bpu2buffer4xi.py
ξ BPU generated ones
...
ξ »gpu2buffer4xi.py
ξ GPU generated ones
...
ξ »zpu2buffer4xi.py
ξ ZPU generated ones

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~WEB4Xi

WEB4Xi

Studio4Xi
ξ studio for the development of multiprocessing4xi and scope4xi »Studio4Xi

Multiprocessing4Xi
ξ multiprocessing services with dragonized trace »Multiprocessing4Xi

select: ~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Device Objects for {BPU ... GPU ... ZPU}

Device Objects for {BPU ... GPU ... ZPU}

DRAGON
ξ base processing unit used to automatically generate device objects to other processing units
ξ »dragon2device4xi.py

(1) Find Model - optional
ξ this step is needed when another working source file is used as a model to create source file to handle device objects
ξ »apu2sampler4xi.py
ξ »apu2sampler4xi5test.py
ξ used as base for device objects

(2) Edit Programs - optional
ξ create source files for the processing unit APU
ξ »apu2device4xi.py
ξ edited Public API comparing to the OpenCL specificatio and removed extra functions and methods
ξ set2device4apu, set2devicecallback4apu and trace2device4apu defined as in any Scope4Xi modules (not in OpenCL specs!)

(3) Set Trace for Programs - once
ξ »print4xi.py
ξ both class and function to all devices {APU ... ZPU} and virtual device {xi}
ξ set debug = True if print4xi.py denies trace

(4) Update Pickle Modules - once
ξ »pickle2a4xi.py
...
ξ »pickle2d4xi.py
ξ special DRAGON processing unit!
...
ξ »pickle2z4xi.py

(5) Test Program for APU (reference processing unit)
ξ processing unit could be any, APU was selected here
ξ »apu2device4xi.py

(6) Fetch Programs for APU in Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or there are others reasons to update dragon program
ξ »fetch2scope4xi.py
ξ »version4xi.py
ξ (6a) define apu2device4xi.py and apu2device4xi5test.py as programs to be fetched in kb2fetch dictionary of fetch2scope4xi.py
ξ (6b) check: path2read4xi # path for input source programs
ξ (6c) check: path2write4xi # path for output source programs
ξ (6d) in command mode >go2studio
ξ (6e) >fetch2scope4xi
ξ »apu2device4xi.py

(7) Generate Dragon modules of Programs for APU to Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or APU has so many changes that a new dragon module is easier to make
ξ (7a) »dragonize2scope4xi.py
ξ (7b) kb2dragonize["apu2device4xi.py"] = "dragon2device4xi.py"
ξ (7c) kb2dragonize["apu2device4xi5test.py"] = "dragon2device4xi5test.py"
ξ (7d) in command mode >dragonize2scope4xi
ξ (7e) »dragon2device4xi.py
ξ (7g) do not delete trace of APU - it has been created in the way that will be dragonize ok

(8) Generate from Dragon Program module modules to {BPU,CPU ... ZPU} - mandatory - {APU} must be skipped
ξ ** warning ** do NOT generate for your reference processing unit, in this case APU processing unit is skipped!
ξ you need one good and real processing unit as master and base for other processing unit
ξ although system could generate source code also to your reference processing unit, do NOT let it do it!
ξ if something goes wrong you'll need the source files of your reference processing unit!
ξ generation may tailor code based on each processing unit capabilities and features!
ξ (8a) »generate2device4scope.py
ξ (8b) edited generator for program using sampler generator as base
ξ (8c) »print4xi.py
ξ (8d) updated trace for Studio4xi
ξ (8e) »pickle2g4xi.py
ξ (8f) updated pickling
ξ (8g) »actor2g4xi.py
ξ (8h) updated actors

(9) Generate
ξ (9a) »generate2device4scope.py
ξ kb2tailor <-- update (if necessary) to generate apu2device4xi.py .. apu2device4xi.py
ξ (9a) »dragon2device4xi.py
ξ (9b) »version4xi.py
ξ (9c) update ActKB4scope dictionary with new module
ξ (9d) ActKB4scope ['z'] ['generate2device4scope'] = 'ACK' # FIRST TO GENERATE BY SETTING TO 'ACK'!
ξ (9e) version4xi.py defines which processing unit device is to be developed - you generate for one at a time
ξ (9f) replace used output ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib <-- ROOT2TEMP4SCOPE:out\lib (empty)
ξ (9g) either >generate2device4scope
ξ (9g) or >python generate2device4scope.py > ROOT2JOB4SCOPE:\04711\studio4xi\cc\generate\out\txt\generate2device4scope.txt
ξ (9h) check ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\generate2device4scope.txt
ξ REMEMBER: version4xi.py ActKB4scope changes for each object and its tester!

(10) Compile one and generate to other processing units
ξ (10a) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\z\zpu2device4xi.py --> ROOT2SCOPE4XI:\041721\zap\lib\z\zpu2device4xi.py
ξ (10b) »zpu2device4xi.py
ξ (10c) compile it!
ξ (10d) ActKB4scope of version4xi.py <-- edit and run for each processing unit - ONE at a time NOT many at the same time!
ξ (10e) take backups from your current Scope4Xi BEFORE proceeding!
ξ (10f) check output programs BEFORE copying them in ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out <-- 25 files in 26 folders!
ξ (10g) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\
ξ (10h) compile all by running all2c - if there are errors you most propably tried to generate several programs in one run!
ξ DONE - you have generated device object modules to processing units {BPU ... GPU ...ZPU} and NOT for {APU}

(11) Generate Device4Xi5test module for ZPU
ξ (11a) skipped because other device objects are being used and tested by other objects

(12) Generate Device4Xi5test module for other devices {BPU ... YPU}
ξ (12a) skipped because other device objects are being used and tested by other objects

(14) Copy generated Program modules to Scope4xi
ξ (14a) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\

(15) Update batch files - once
ξ only once - skipped in this version

(16) Compile and test Program modules all processing units
ξ (16a) >all2c in command mode of Scope4xi
ξ (16b) ROOT2SCOPE4XI:\041721\zap\work\txt <-- see that all are updated, check some if any there are FAILED messages
ξ (16c) ROOT2SCOPE4XI:\041721\zap\web\xml <-- see that all are updated and browser some

(17) DONE
ξ backup ROOT2SCOPE4XI:\041721
ξ backup ROOT2JOB4SCOPE:\041721

1) APU reference processing unit ones created with physical processing unit
ξ »apu2device4xi.py

2) DRAGON processing unit ones created from APU and used to automatically by software to generate software for {BPU ... GPU ... ZPU}
ξ »dragon2device4xi.py

3) Device objects for processing units {BPU ... GPU ... ZPU}
ξ »bpu2device4xi.py
ξ BPU generated ones
...
ξ »gpu2device4xi.py
ξ GPU generated ones
...
ξ »zpu2device4xi.py
ξ ZPU generated ones

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Pickling

Pickling

ξ »pickle2a4xi.py
ξ »pickle2b4xi.py
ξ »pickle2c4xi.py
ξ »pickle2d4xi.py
ξ »pickle2e4xi.py
ξ »pickle2f4xi.py
ξ »pickle2g4xi.py
ξ »pickle2h4xi.py
ξ »pickle2i4xi.py
ξ »pickle2j4xi.py
ξ »pickle2k4xi.py
ξ »pickle2l4xi.py
ξ »pickle2m4xi.py
ξ »pickle2n4xi.py
ξ »pickle2o4xi.py
ξ »pickle2p4xi.py
ξ »pickle2q4xi.py
ξ »pickle2r4xi.py
ξ »pickle2s4xi.py
ξ »pickle2t4xi.py
ξ »pickle2u4xi.py
ξ »pickle2v4xi.py
ξ »pickle2w4xi.py
ξ »pickle2x4xi.py
ξ »pickle2y4xi.py
ξ »pickle2z4xi.py

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Actors

Actors

ξ »actor2a4xi.py
ξ »actor2b4xi.py
ξ »actor2c4xi.py
ξ »actor2d4xi.py
ξ »actor2e4xi.py
ξ »actor2f4xi.py
ξ »actor2g4xi.py
ξ »actor2h4xi.py
ξ »actor2i4xi.py
ξ »actor2j4xi.py
ξ »actor2k4xi.py
ξ »actor2l4xi.py
ξ »actor2m4xi.py
ξ »actor2n4xi.py
ξ »actor2o4xi.py
ξ »actor2p4xi.py
ξ »actor2q4xi.py
ξ »actor2r4xi.py
ξ »actor2s4xi.py
ξ »actor2t4xi.py
ξ »actor2u4xi.py
ξ »actor2v4xi.py
ξ »actor2w4xi.py
ξ »actor2x4xi.py
ξ »actor2y4xi.py
ξ »actor2z4xi.py
ξ multiprocessing4xi actors
ξ OpenCL actors - classes and functions

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Parsing

Parsing

ξ »parse2scope4xi.py
ξ »parse2scope4xi.txt

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Trace (Print4Xi)

Trace (Print4Xi)

ξ »print4xi.py
ξ trace

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Nouns for modules

Nouns for modules

ξ explored

ξ the rest of the OpenCL objects + scope objects + zeta objects + series + processing units + general nouns + special nouns
ξ [ ] A - [ ] ace [ ] act [ ] action [ ] aframe [ ] alpha [ ] aperture [ ] arc [ ] assets
ξ [ ] B - [ ] bpu [ ] balance [ ] barrier [ ] base [ ] beat [ ] beta [ ] bpu [ ] build [ ] burst
ξ [ ] C - [ ] camera [ ] cast [ ] cell [ ] charge [ ] checkpoint [ ] core [ ] cue [ ] cutback
ξ [ ] D - [ ] defense [ ] delivery [ ] delta [ ] deployment [ ] direction [ ] distance [ ] dragon [ ] dude
ξ [ ] E - [ ] epu [ ] ecosystem [ ] energy [ ] engine [ ] environment [ ] epsilon [ ] event [ ] exposure
ξ [ ] F - [ ] fpu [ ] field [ ] fire [ ] flow [ ] focus [ ] force [ ] front [ ] fusion
ξ [ ] G - [ ] gage [ ] game [ ] gamma [ ] gap [ ] goal [ ] grid [ ] group [ ] gun
ξ [ ] H - [ ] hpu [ ] hatch [ ] head [ ] health [ ] hit [ ] hide [ ] hold [ ] hollow
ξ [ ] I - [ ] ipu [ ] identication [ ] igniter [ ] image [ ] incide [ ] infiltration [ ] intelligence [ ] inspection [ ] issue
ξ [ ] J - [ ] jpu [ ] jack [ ] jib [ ] job [ ] joint [ ] joist [ ] judder [ ] junction
ξ [ ] K - [ ] kpu [ ] keg [ ] kernel [ ] kicker [ ] kickoff [ ] kink [ ] knowledge [ ] kyle
ξ [ ] L - [ ] lpu [ ] lambda [ ] layback [ ] layer [ ] lens [ ] lighting [ ] load [ ] lull
ξ [ ] M - [ ] mpu [ ] magazine [ ] maneuver [ ] mark [ ] math [ ] maverick [ ] memobject [ ] mission
ξ [ ] N - [ ] npu [ ] narration [ ] ndrange [ ] net [ ] normalize [ ] notify [ ] nose [ ] nuclear
ξ [ ] O - [ ] opu [ ] obstacle [ ] ocean [ ] Orchestra [ ] offshore [ ] operation [ ] origin [ ] overlay
ξ [ ] P - [ ] pace [ ] payload [ ] pipeline [ ] pitch [ ] pool [ ] power [ ] profile [ ] program
ξ [ ] Q - [ ] qpu [ ] qualifier [ ] quality [ ] guiver [ ] quince [ ] quipu [ ] query [ ] quiz
ξ [ ] R - [ ] rail [ ] ray [ ] reasoner [ ] receiver [ ] render [ ] resource [ ] rip [ ] router
ξ [ ] S - [ ] sampler [ ] scene [ ] scope [ ] sensor [ ] script [ ] sphere [ ] source [ ] shadow
ξ [ ] T - [ ] tpu [ ] target [ ] task [ ] talent [ ] texture [ ] theater [ ] tone [ ] turtle
ξ [ ] U - [ ] upu [ ] union [ ] unload [ ] unmap [ ] ubity [ ] underexposure [ ] upas [ ] usage
ξ [ ] V - [ ] vector [ ] vendor [ ] venerer [ ] venue [ ] video [ ] visibility [ ] voice [ ] voxel
ξ [ ] W - [ ] wpu [ ] waitlist [ ] wave [ ] wing [ ] wipeout [ ] workitem [ ] worklist [ ] workgroup
ξ [ ] X - [ ] xpu [ ] xenops [ ] xi [ ] xray [ ] xylem [ ] xyster [ ] xyston [ ] xystus
ξ [ ] Y - [ ] ypu [ ] yabba [ ] yacht [ ] yad [ ] yarn [ ] yielder [ ] yag [ ] yeast
ξ [ ] Z - [ ] zpu [ ] zabra [ ] zambra [ ] zanze [ ] zero [ ] zarf [ ] zeta [ ] zone

Links (at a time being)
ξ »Space
ξ »Arts
ξ »Law
ξ »Wines
ξ »Science
ξ »Business
ξ »Photography
ξ »Green Living Tips
ξ »Fishing
ξ »Movie Terminology Glossary
ξ »Animation
ξ »Music
ξ »Dance & Theatre Terms
ξ »Snowboarding
ξ »Surfing Waves
ξ »Phrontistery
ξ »FAS Lexicon

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Skeleton

Skeleton

ξ »z2skeleton4xi.py
ξ »z2skeleton4xi5test.py
ξ »z2skeleton4xi5test.txt
ξ »sense-z2skeleton4xi5test.xml
ξ »reason-z2skeleton4xi5test.xml
ξ »ace-test-z2skeleton4xi5test.xml
ξ skeleton for Scope4Xi modules - with dragonized tagging

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Version

Version

ξ »version4xi.py
ξ each alphabet folder has this module
ξ this makes importing much easier to programs

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Miscellaneous

Miscellaneous

ξ »zapimport2ball4xi.py
ξ imports zapped Python module with 3D-shots and creates HTML file
ξ »yoke4xi.py
ξ yoke = to join - in this case input to multiple channels

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Sense XML Files

Sense XML Files

ξ »sense-apu2commandqueue4xi5test
ξ »sense-bpu2commandqueue4xi5test
ξ »sense-cpu2commandqueue4xi5test
ξ »sense-dpu2commandqueue4xi5test
ξ »sense-epu2commandqueue4xi5test
ξ »sense-fpu2commandqueue4xi5test
ξ »sense-gpu2commandqueue4xi5test
ξ »sense-hpu2commandqueue4xi5test
ξ »sense-ipu2commandqueue4xi5test
ξ »sense-jpu2commandqueue4xi5test
ξ »sense-kpu2commandqueue4xi5test
ξ »sense-lpu2commandqueue4xi5test
ξ »sense-mpu2commandqueue4xi5test
ξ »sense-npu2commandqueue4xi5test
ξ »sense-opu2commandqueue4xi5test
ξ »sense-ppu2commandqueue4xi5test
ξ »sense-qpu2commandqueue4xi5test
ξ »sense-rpu2commandqueue4xi5test
ξ »sense-spu2commandqueue4xi5test
ξ »sense-tpu2commandqueue4xi5test
ξ »sense-upu2commandqueue4xi5test
ξ »sense-vpu2commandqueue4xi5test
ξ »sense-xpu2commandqueue4xi5test
ξ »sense-wpu2commandqueue4xi5test
ξ »sense-ypu2commandqueue4xi5test
ξ »sense-zpu2commandqueue4xi5test

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Reason XML Files

Reason XML Files

ξ »reason-apu2commandqueue4xi5test
ξ »reason-bpu2commandqueue4xi5test
ξ »reason-cpu2commandqueue4xi5test
ξ »reason-dpu2commandqueue4xi5test
ξ »reason-epu2commandqueue4xi5test
ξ »reason-fpu2commandqueue4xi5test
ξ »reason-gpu2commandqueue4xi5test
ξ »reason-hpu2commandqueue4xi5test
ξ »reason-ipu2commandqueue4xi5test
ξ »reason-jpu2commandqueue4xi5test
ξ »reason-kpu2commandqueue4xi5test
ξ »reason-lpu2commandqueue4xi5test
ξ »reason-mpu2commandqueue4xi5test
ξ »reason-npu2commandqueue4xi5test
ξ »reason-opu2commandqueue4xi5test
ξ »reason-ppu2commandqueue4xi5test
ξ »reason-qpu2commandqueue4xi5test
ξ »reason-rpu2commandqueue4xi5test
ξ »reason-spu2commandqueue4xi5test
ξ »reason-tpu2commandqueue4xi5test
ξ »reason-upu2commandqueue4xi5test
ξ »reason-vpu2commandqueue4xi5test
ξ »reason-xpu2commandqueue4xi5test
ξ »reason-wpu2commandqueue4xi5test
ξ »reason-ypu2commandqueue4xi5test
ξ »reason-zpu2commandqueue4xi5test

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Ace XML Files

Ace XML Files

ξ »ace-apu2commandqueue4xi5test
ξ »ace-bpu2commandqueue4xi5test
ξ »ace-cpu2commandqueue4xi5test
ξ »ace-dpu2commandqueue4xi5test
ξ »ace-epu2commandqueue4xi5test
ξ »ace-fpu2commandqueue4xi5test
ξ »ace-gpu2commandqueue4xi5test
ξ »ace-hpu2commandqueue4xi5test
ξ »ace-ipu2commandqueue4xi5test
ξ »ace-jpu2commandqueue4xi5test
ξ »ace-kpu2commandqueue4xi5test
ξ »ace-lpu2commandqueue4xi5test
ξ »ace-mpu2commandqueue4xi5test
ξ »ace-npu2commandqueue4xi5test
ξ »ace-opu2commandqueue4xi5test
ξ »ace-ppu2commandqueue4xi5test
ξ »ace-qpu2commandqueue4xi5test
ξ »ace-rpu2commandqueue4xi5test
ξ »ace-spu2commandqueue4xi5test
ξ »ace-tpu2commandqueue4xi5test
ξ »ace-upu2commandqueue4xi5test
ξ »ace-vpu2commandqueue4xi5test
ξ »ace-xpu2commandqueue4xi5test
ξ »ace-wpu2commandqueue4xi5test
ξ »ace-ypu2commandqueue4xi5test
ξ »ace-zpu2commandqueue4xi5test

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~Test Files

Test Files

~Studio4Xi

Studio4Xi

ξ ../../../../../studio4xi/python/3.3/bat/*.bat
ξ batch files create output text files automatically

ξ »find2py4scope.py
ξ ../../../lib --> ROOT2STUDIO4TXT:/find2py4scope.txt

ξ »find2text4scope.py
ξ ../../../work/txt/ --> ROOT2STUDIO4TXT:/find2text4scope.txt

ξ »find2xml4scope.py
ξ ../../../web/xml --> ROOT2STUDIO4TXT:/find2xml4scope.txt

ξ »parse2scope4xi
ξ \lib --> ../../../txt/parse2scope4xi.txt

ξ »version4xi.py
ξ knowledgebase for access paths --> ROOT2STUDIO4TXT:/parsescope4xi.txt

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Verbs

Verbs

ξ »verb4xi.py
ξ »verb2a4xi.py
ξ »verb2ba4xi.py
ξ »verb2c4xi.py
ξ »verb2d4xi.py
ξ »verb2e4xi.py
ξ »verb2f4xi.py
ξ »verb2g4xi.py
ξ »verb2h4xi.py
ξ »verb2i4xi.py
ξ »verb2j4xi.py
ξ »verb2k4xi.py
ξ »verb2l4xi.py
ξ »verb2m4xi.py
ξ »verb2n4xi.py
ξ »verb2o4xi.py
ξ »verb2p4xi.py
ξ »verb2q4xi.py
ξ »verb2r4xi.py
ξ »verb2s4xi.py
ξ »verb2t4xi.py
ξ »verb2u4xi.py
ξ »verb2v4xi.py
ξ »verb2w4xi.py
ξ »verb2x4xi.py
ξ »verb2y4xi.py
ξ »verb2z4xi.py
ξ »verb2_4xi.py
ξ verbs in system

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Event Objects for {BPU ... GPU ... ZPU}

Event Objects for {BPU ... GPU ... ZPU}

DRAGON
ξ base processing unit used to automatically generate event objects to other processing units
ξ »dragon2event4xi.py

(1) Find Model - optional
ξ this step is needed when another working source file is used as a model to create source file to handle event objects
ξ »apu2sampler4xi.py
ξ »apu2sampler4xi5test.py
ξ used as base for event objects

(2) Edit Programs - optional
ξ create source files for the processing unit APU
ξ »apu2event4xi.py
ξ »apu2event4xi5test.py
ξ edited Public API comparing to the OpenCL specificatio and removed extra functions and methods
ξ set2event4apu, set2eventcallback4apu and trace2event4apu defined as in any Scope4Xi modules (not in OpenCL specs!)

(3) Set Trace for Programs - once
ξ »print4xi.py
ξ both class and function to all events {APU ... ZPU} and virtual event {xi}
ξ set debug = True if print4xi.py denies trace

(4) Update Pickle Modules - once
ξ »pickle2a4xi.py
...
ξ »pickle2d4xi.py
ξ special DRAGON processing unit!
...
ξ »pickle2z4xi.py

(5) Test Program for APU (reference processing unit)
ξ processing unit could be any, APU was selected here
ξ »apu2event4xi.py
ξ »apu2event4xi5test.py
ξ »apu2event4xi5test.txt
ξ »ace-apu2event4xi5test
ξ »reason-apu2event4xi5test
ξ »sense-apu2event4xi5test

(6) Fetch Programs for APU in Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or there are others reasons to update dragon program
ξ »fetch2scope4xi.py
ξ »version4xi.py
ξ (6a) define apu2event4xi.py and apu2event4xi5test.py as programs to be fetched in kb2fetch dictionary of fetch2scope4xi.py
ξ (6b) check: path2read4xi # path for input source programs
ξ (6c) check: path2write4xi # path for output source programs
ξ (6d) in command mode >go2studio
ξ (6e) >fetch2scope4xi
ξ »apu2event4xi.py
ξ »apu2event4xi5test.py

(7) Generate Dragon modules of Programs for APU to Studio4Xi - optional
ξ this step is needed only if dragon module has not been created or APU has so many changes that a new dragon module is easier to make
ξ (7a) »dragonize2scope4xi.py
ξ (7b) kb2dragonize["apu2event4xi.py"] = "dragon2event4xi.py"
ξ (7c) kb2dragonize["apu2event4xi5test.py"] = "dragon2event4xi5test.py"
ξ (7d) in command mode >dragonize2scope4xi
ξ (7e) »dragon2event4xi.py
ξ (7f) »dragon2event4xi5test.py
ξ (7g) do not delete trace of APU - it has been created in the way that will be dragonize ok

(8) Generate from Dragon Program module modules to {BPU,CPU ... ZPU} - mandatory - {APU} must be skipped
ξ ** warning ** do NOT generate for your reference processing unit, in this case APU processing unit is skipped!
ξ you need one good and real processing unit as master and base for other processing unit
ξ although system could generate source code also to your reference processing unit, do NOT let it do it!
ξ if something goes wrong you'll need the source files of your reference processing unit!
ξ generation may tailor code based on each processing unit capabilities and features!
ξ (8a) »generate2event4scope.py
ξ (8b) edited generator for program using sampler generator as base
ξ (8c) »print4xi.py
ξ (8d) updated trace for Studio4xi
ξ (8e) »pickle2g4xi.py
ξ (8f) updated pickling
ξ (8g) »actor2g4xi.py
ξ (8h) updated actors

(9) Generate
ξ (9a) »generate2event4scope.py
ξ kb2tailor <-- update (if necessary) to generate apu2event4xi.py .. apu2event4xi.py
ξ (9a) »dragon2event4xi.py
ξ (9b) »version4xi.py
ξ (9c) update ActKB4scope dictionary with new module
ξ (9d) ActKB4scope ['z'] ['generate2event4scope'] = 'ACK' # FIRST TO GENERATE BY SETTING TO 'ACK'!
ξ (9e) version4xi.py defines which processing unit event is to be developed - you generate for one at a time
ξ (9f) replace used output ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib <-- ROOT2TEMP4SCOPE:out\lib (empty)
ξ (9g) either >generate2event4scope
ξ (9g) or >python generate2event4scope.py > ROOT2JOB4SCOPE:\04711\studio4xi\cc\generate\out\txt\generate2event4scope.txt
ξ (9h) check ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\generate2event4scope.txt
ξ REMEMBER: version4xi.py ActKB4scope changes for each object and its tester!

(10) Compile one and generate to other processing units
ξ (10a) ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\z\zpu2event4xi.py --> ROOT2SCOPE4XI:\041721\zap\lib\z\zpu2event4xi.py
ξ (10b) »zpu2event4xi.py
ξ (10c) compile it!
ξ (10d) ActKB4scope of version4xi.py <-- edit and run for each processing unit - ONE at a time NOT many at the same time!
ξ (10e) take backups from your current Scope4Xi BEFORE proceeding!
ξ (10f) check output programs BEFORE copying them in ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out <-- 25 files in 26 folders!
ξ (10g) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\
ξ (10h) compile all by running all2c - if there are errors you most propably tried to generate several programs in one run!
ξ DONE - you have generated event object modules to processing units {BPU ... GPU ...ZPU} and NOT for {APU}

(11) Generate Commandqueue4Xi5test modules as above
ξ (11a) »generate2event4scope.py
ξ define test module: kb2tailor ['b'] ['module'] = 'bpu2event4xi5test.py' ... kb2tailor ['z'] ['module'] = 'zpu2event4xi5test.py'
ξ (11b) »version4xi.py
ξ as above ActKB4scope ['b'] ['generate2event4scope'] = 'ACK' ... ActKB4scope ['z'] ['generate2event4scope'] = 'ACK' one at a time

(14) Copy generated Program modules to Scope4xi
ξ (14a) copy generated programs to Scope4Xi ROOT2JOB4SCOPE:\041721\studio4xi\cc\generate\out\lib\ --> ROOT2SCOPE4XI:\041721\zap\lib\

(15) Update batch files - once
ξ only once - skipped in this version

(16) Compile and test Program modules all processing units
ξ (16a) >all2c in command mode of Scope4xi
ξ (16b) ROOT2SCOPE4XI:\041721\zap\work\txt <-- see that all are updated, check some if any there are FAILED messages
ξ (16c) ROOT2SCOPE4XI:\041721\zap\web\xml <-- see that all are updated and browser some

(17) DONE
ξ backup ROOT2SCOPE4XI:\041721
ξ backup ROOT2JOB4SCOPE:\041721

1) APU reference processing unit ones created with physical processing unit
ξ »apu2event4xi.py
ξ »apu2event4xi5test.py

2) DRAGON processing unit ones created from APU and used to automatically by software to generate software for {BPU ... GPU ... ZPU}
ξ »dragon2event4xi.py
ξ »dragon2event4xi5test.py

3) Commandqueue objects for processing units {BPU ... GPU ... ZPU}
ξ »bpu2event4xi.py
ξ »bpu2event4xi5test.py
ξ BPU generated ones
...
ξ »gpu2event4xi.py
ξ »gpu2event4xi5test.py
ξ GPU generated ones
...
ξ »zpu2event4xi.py
ξ »zpu2event4xi5test.py
ξ ZPU generated ones

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Buffers

Buffers

ξ »buffer4xi.py
ξ Xi device buffers
ξ »buffer4xi5test.py
ξ Xi device buffers tests

ξ »apu2buffer4xi.py
ξ »bpu2buffer4xi.py
ξ »cpu2buffer4xi.py
ξ »dpu2buffer4xi.py
ξ »epu2buffer4xi.py
ξ »fpu2buffer4xi.py
ξ »gpu2buffer4xi.py
ξ »hpu2buffer4xi.py
ξ »ipu2buffer4xi.py
ξ »jpu2buffer4xi.py
ξ »kpu2buffer4xi.py
ξ »lpu2buffer4xi.py
ξ »mpu2buffer4xi.py
ξ »npu2buffer4xi.py
ξ »opu2buffer4xi.py
ξ »ppu2buffer4xi.py
ξ »qpu2buffer4xi.py
ξ »rpu2buffer4xi.py
ξ »spu2buffer4xi.py
ξ »tpu2buffer4xi.py
ξ »upu2buffer4xi.py
ξ »vpu2buffer4xi.py
ξ »xpu2buffer4xi.py
ξ »wpu2buffer4xi.py
ξ »ypu2buffer4xi.py
ξ »zpu2buffer4xi.py
ξ buffers for each device APU ... ZPU

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ API

API

ξ »buffer4xi.py

ξ »commandqueue4xi.py
ξ »commandqueue4xi5test.py

ξ »context4xi.py

ξ »device4xi.py
ξ »device4xi5test.py

ξ »event4xi.py
ξ »event4xi5test.py

ξ »image2d4xi.py
ξ »image2d4xi5test.py

ξ »image3d4xi.py
ξ »image3d4xi5test.py

ξ »kernel4xi.py
ξ »kernel4xi5test.py

ξ »platformids4xi.py
ξ »platformids4xi5test.py

ξ »platforminfo4xi.py
ξ »platforminfo4xi5test.py

ξ »program4xi.py
ξ »program4xi5test.py

ξ »sampler4xi.py
ξ »sampler4xi5test.py

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ import2ball4xi

import2ball4xi

ξ »zapimport2ball4xi.py
ξ main program

ξ »import2ball4xi.py
ξ the one doing the job

ξ »sense-hello-world4xi.html
ξ sense example
ξ view source in browser - data in designed for web apps
ξ HTML file generated depends on the input file selected
ξ »reason-hello-pipe4xi.html
ξ reason example
ξ »ace-test-arena4xi.html
ξ ace example

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Compiling and testing

Compiling and testing

all2core
ξ compiles all core folders!

dragon2c
ξ compiles dragon-subfolder which has master modules to generate programs for devices {BPU,CPU...GPU ... ZPU}, where APU is excluded
ξ tests included!

a2c ... z2c
ξ each one compiles the corresponding alphabetic subfolder
ξ tests included!

all2c
ξ compiling all !
ξ tests included!

run4xi
ξ used to a current job

ξ »Keyboard profiles and commands

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Special programs

Special programs

version4xi.py
ξ »version4xi.py
ξ exists in all folders, master in /v/
ξ makes it easier to import functions and classes without having to worry from where they must be imported
ξ the same content in all subfolders

ξ »version4riika.py
ξ special version, master in /v/ and is being copied to all other subfolder automatically due to go2scope4xi command
ξ automatic copy makes sure version4xi.py gets corrected to proper workstation version if contents have been downloaded from web

apu2dummy4xi5test.cpp ... zpu2dummy4xi5test.cpp
ξ »apu2dummy4xi5test.cpp

import2ball4xi
ξ »import2ball4xi.py

yoke4xi
ξ »yoke4xi.py

zapimport2ball4xi
ξ »zapimport2ball4xi.py

z2skeleton4xi
ξ »z2skeleton4xi.py
ξ »z2skeleton4xi5test.py

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Program tags

~ Dragon processing unit

Dragon processing unit

ξ base processing unit DRAGON used to automatically generate software for real processing units {APU ... GPU ... ZPU}

ξ »dragon2buffer4xi

ξ »dragon2commandqueue4xi
ξ »dragon2commandqueue4xi5test

ξ »dragon2context4xi

ξ »dragon2device4xi

ξ »dragon2event4xi
ξ »dragon2event4xi5test

ξ »dragon2image4xi
ξ »dragon2image4xi5test

ξ »dragon2kernel4xi
ξ »dragon2kernel4xi5test

ξ »dragon2program4xi
ξ »dragon2program4xi5test

ξ »dragon2sampler4xi
ξ »dragon2sampler4xi5test

ξ »dragon3image4xi
ξ »dragon3image4xi5test

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Walktrough and Overview

Walktrough and Overview

Common

»

Environment

»

Links to DragonXi

»

Keyboard profiles and commands

»

Includes of OpenCL

»

To-be-done

»

New Module Development

»

Memory mapping and Arena4Xi

»

Xi Device

»

Macros for Trace Messages

»

Getting whole or part of info

»

Nouns4Xi - Model for Command & Control

»

Unresolved temporary

»

2D Image Objects

»

3D Image Objects

»

Context Objects

»

State Machine or Thread

»

Sampler Objects

»

Actors

»

Picklers

»

Program Objects

»

APU Test Modules

»

Special cases in tracing

»

Kernel Objects

»

Tracing Xi Device Modules

»

Command Queue Objects

»

Buffers

»

WEB4Xi

»

Devices

»

Pickling

»

Actors

»

Parsing

»

Trace

»

Nouns for modules

»

Skeleton

»

Version

»

Miscellaneous

»

Sense XML Files

»

Reason XML Files

»

Ace XML Files

»

Test Files

»

Studio4Xi

»

Verbs

»

Events

»

Buffers

»

API

»

import2ball4xi

»

Compiling and testing

»

Special programs

»

Program tags

»

Dragon processing unit

»

Walktrough and Overview

»

Parsing Scope4Xi modules in Studio4Xi

»

Generating automatically programs

»

041721 conversion

»

Dragon Concept

»

Forums

»

BLOG

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Parsing Scope4Xi modules in Studio4Xi

Parsing Scope4Xi modules in Studio4Xi

ξ »parse2scope4xi.py
ξ »parse2scope4xi.txt

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Generating automatically programs

Generating automatically programs

ξ »Sampler Objects & generating them
ξ »Program Objects & Generating them
ξ »Kernel Objects
ξ all programs found in OpenCl specifications
ξ all those with name not starting with device such as {apu ... zpu}

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ 041721 conversion

041721 conversion

I. Find 041711, python32, python3.2

1. >go3studio4fb

2. edit E:\STUDIO4XI\Python\3.3\src\find2py4scope.py
ice_find_s1="041711" #
ice_find_s2='python32' #
ice_find_s3='python3.2' #
ice_find_s4='32.pyc' #
ice_find_s5='32'
ice_find_s6='3.2

3. >find2py4scope

4. viewed ROOT2STUDIO4TXT:/find2py4scope.txt
ACK IN FILE <-- search these line with macro
xml-file location data must be converted in all modules which build xml-files:
ξ path2xml4scope
ξ context2sense
ξ context2reason
ξ context2ace

python32 paths must be changed to python33
ξ name_space4xi
ξ xml_base4xi
ξ xml_base4xi

5. edited E:\STUDIO4XI\Python\3.3\src\find2py4scope.py
ξ limited search to one subfolder at a time to make it easier to find the modules to be changed
ξ subfolder a is used to create master modules for dragon folder
ξ added dragon folder to version4xi.py in Studio4Xi
ξ run find2py4scope in Studio4Xi

6. checked modules in each folder by running find2scope4xi with search patterns
ξ kept this file open
ξ kept find2py4scope.py open and changed subfolder to be searched
ξ find2pyscope.txt open and refreshed for each round
ξ *.py opened in the folder being processed
ξ dir > x2scope.txt in each subfolder x
ξ run > find2py2scope in studio4xi and then view find2pyscope.txt enough times to get everyhting changed

[a]

ξ »apu2buffer4xi
ξ »apu2commandqueue4xi
ξ »apu2commandqueue4xi5test
ξ »apu2context4xi
ξ »apu2device4xi
ξ »apu2dummy4xi5test
ξ »apu2event4xi
ξ »apu2event4xi5test
ξ »apu2image4xi
ξ »apu2image4xi5test
ξ »apu2kernel4xi
ξ »apu2kernel4xi5test
ξ »apu2program4xi
ξ »apu2program4xi5test
ξ »apu2sampler4xi
ξ »apu2sampler4xi5test
ξ »apu3image4xi
ξ »apu3image4xi5test
compiled: > a2c

[b] special: buffer4xi.py

ξ »bpu2buffer4xi
ξ »bpu2commandqueue4xi
ξ »bpu2commandqueue4xi5test
ξ »bpu2context4xi
ξ »bpu2device4xi
ξ »bpu2dummy4xi5test
ξ »bpu2event4xi
ξ »bpu2event4xi5test
ξ »bpu2image4xi
ξ »bpu2image4xi5test
ξ »bpu2kernel4xi
ξ »bpu2kernel4xi5test
ξ »bpu2program4xi
ξ »bpu2program4xi5test
ξ »bpu2sampler4xi
ξ »bpu2sampler4xi5test
ξ »bpu3image4xi
ξ »bpu3image4xi5test
ξ »buffer4xi
ξ »buffer4xi5test
ξ »version4xi
compiled: > b2c

[c] special: commandqueue4xi.py context4xi.py

ξ »commandqueue4xi
ξ »commandqueue4xi5test
ξ »context4xi
ξ »context4xi5test
ξ »cpu2buffer4xi
ξ »cpu2commandqueue4xi
ξ »cpu2commandqueue4xi5test
ξ »cpu2context4xi
ξ »cpu2device4xi
ξ »cpu2device4xi5test
ξ »cpu2dummy4xi5test
ξ »cpu2event4xi
ξ »cpu2event4xi5test
ξ »cpu2image4xi
ξ »cpu2image4xi5test
ξ »cpu2kernel4xi
ξ »cpu2kernel4xi5test
ξ »cpu2program4xi
ξ »cpu2program4xi5test
ξ »cpu2sampler4xi
ξ »cpu2sampler4xi5test
ξ »cpu3image4xi
ξ »cpu3image4xi5test
ξ »version4xi
compiled: > c2c

[d] special: device

ξ »device4xi
ξ »device4xi5test
ξ »dpu2buffer4xi
ξ »dpu2commandqueue4xi
ξ »dpu2commandqueue4xi5test
ξ »dpu2context4xi
ξ »dpu2device4xi
ξ »dpu2dummy4xi5test
ξ »dpu2event4xi
ξ »dpu2event4xi5test
ξ »dpu2image4xi
ξ »dpu2image4xi5test
ξ »dpu2kernel4xi
ξ »dpu2kernel4xi5test
ξ »dpu2program4xi
ξ »dpu2program4xi5test
ξ »dpu2sampler4xi
ξ »dpu2sampler4xi5test
ξ »dpu3image4xi
ξ »dpu3image4xi5test
ξ »version4xi
compiled: > d2c

[d] special: all - these are used as models to generate programs to devices!
context2sense, context2reason, context2ace <-- changed based on available domains
ξ changed name_space4xi and xml_base4xi in *5test.py

ξ »dragon2dummy4xi5test
ξ »dragon2image4xi
ξ »dragon2image4xi5test
ξ »dragon2kernel4xi
ξ »dragon2kernel4xi5test
ξ »dragon2program4xi
ξ »dragon2program4xi5test
ξ »dragon2sampler4xi
ξ »dragon3image4xi
ξ »dragon3image4xi5test
ξ »version4xi
tried to compile: > dragon2c - it ** requires dragonizing ALL modules **

[e] special: event4xi
ξ »epu2buffer4xi
ξ »epu2commandqueue4xi
ξ »epu2commandqueue4xi5test
ξ »epu2context4xi
ξ »epu2device4xi
ξ »epu2dummy4xi5test
ξ »epu2event4xi
ξ »epu2event4xi5test
ξ »epu2image4xi
ξ »epu2image4xi5test
ξ »epu2kernel4xi
ξ »epu2kernel4xi5test
ξ »epu2program4xi
ξ »epu2program4xi5test
ξ »epu2sampler4xi
ξ »epu2sampler4xi5test
ξ »epu3image4xi
ξ »epu3image4xi5test
ξ »event4xi
ξ »event4xi5test
ξ »version4xi

compiled: > e2c

[f] special: None
ξ »fpu2buffer4xi
ξ »fpu2commandqueue4xi
ξ »fpu2commandqueue4xi5test
ξ »fpu2context4xi
ξ »fpu2device4xi
ξ »fpu2dummy4xi5test
ξ »fpu2event4xi
ξ »fpu2event4xi5test
ξ »fpu2image4xi
ξ »fpu2image4xi5test
ξ »fpu2kernel4xi
ξ »fpu2kernel4xi5test
ξ »fpu2program4xi
ξ »fpu2program4xi5test
ξ »fpu2sampler4xi
ξ »fpu2sampler4xi5test
ξ »fpu3image4xi
ξ »fpu3image4xi5test
ξ »version4xi

compiled: > f2c

[g] special: None
ξ »gpu2buffer4xi
ξ »gpu2commandqueue4xi
ξ »gpu2commandqueue4xi5test
ξ »gpu2context4xi
ξ »gpu2device4xi
ξ »gpu2device4xi5test
ξ »gpu2dummy4xi5test
ξ »gpu2event4xi
ξ »gpu2event4xi5test
ξ »gpu2image4xi
ξ »gpu2image4xi5test
ξ »gpu2kernel4xi
ξ »gpu2kernel4xi5test
ξ »gpu2program4xi
ξ »gpu2program4xi5test
ξ »gpu2sampler4xi
ξ »gpu2sampler4xi5test
ξ »gpu3image4xi
ξ »gpu3image4xi5test
ξ »version4xi

[h] special: None
ξ »hpu2buffer4xi
ξ »hpu2commandqueue4xi
ξ »hpu2commandqueue4xi5test
ξ »hpu2context4xi
ξ »hpu2device4xi
ξ »hpu2dummy4xi5test
ξ »hpu2event4xi
ξ »hpu2event4xi5test
ξ »hpu2image4xi
ξ »hpu2image4xi5test
ξ »hpu2kernel4xi
ξ »hpu2kernel4xi5test
ξ »hpu2program4xi
ξ »hpu2program4xi5test
ξ »hpu2sampler4xi
ξ »hpu2sampler4xi5test
ξ »hpu3image4xi
ξ »hpu3image4xi5test
ξ »version4xi

[i] special: image2d4xi image3d4xi import2ball4xi
ξ »image2d4xi
ξ »image2d4xi5test
ξ »image3d4xi
ξ »image3d4xi5test
ξ »import2ball4xi
ξ »ipu2buffer4xi
ξ »ipu2commandqueue4xi
ξ »ipu2commandqueue4xi5test
ξ »ipu2context4xi
ξ »ipu2device4xi
ξ »ipu2dummy4xi5test
ξ »ipu2event4xi
ξ »ipu2event4xi5test
ξ »ipu2image4xi
ξ »ipu2image4xi5test
ξ »ipu2kernel4xi
ξ »ipu2kernel4xi5test
ξ »ipu2program4xi
ξ »ipu2program4xi5test
ξ »ipu2sampler4xi
ξ »ipu2sampler4xi5test
ξ »ipu3image4xi
ξ »ipu3image4xi5test
ξ »version4xi

compiled: > i2c

[j] special: None
ξ »jpu2buffer4xi
ξ »jpu2commandqueue4xi
ξ »jpu2commandqueue4xi5test
ξ »jpu2context4xi
ξ »jpu2device4xi
ξ »jpu2dummy4xi5test
ξ »jpu2event4xi
ξ »jpu2event4xi5test
ξ »jpu2image4xi
ξ »jpu2image4xi5test
ξ »jpu2kernel4xi
ξ »jpu2kernel4xi5test
ξ »jpu2program4xi
ξ »jpu2program4xi5test
ξ »jpu2sampler4xi
ξ »jpu2sampler4xi5test
ξ »jpu3image4xi
ξ »jpu3image4xi5test
ξ »version4xi

compiled: > j2c

[k] special: kernel4xi
ξ »kernel4xix
ξ »kernel4xi5testx
ξ »kpu2buffer4xix
ξ »kpu2commandqueue4xix
ξ »kpu2commandqueue4xi5testx
ξ »kpu2context4xix
ξ »kpu2device4xix
ξ »kpu2dummy4xi5testx
ξ »kpu2event4xix
ξ »kpu2event4xi5testx
ξ »kpu2image4xix
ξ »kpu2image4xi5testx
ξ »kpu2kernel4xix
ξ »kpu2kernel4xi5testx
ξ »kpu2program4xix
ξ »kpu2program4xi5testx
ξ »kpu2sampler4xix
ξ »kpu2sampler4xi5testx
ξ »kpu3image4xix
ξ »kpu3image4xi5testx
ξ »version4xix

compiled: > k2c

[l] special: None
ξ »lpu2buffer4xix
ξ »lpu2commandqueue4xix
ξ »lpu2commandqueue4xi5testx
ξ »lpu2context4xix
ξ »lpu2device4xix
ξ »lpu2dummy4xi5testx
ξ »lpu2event4xix
ξ »lpu2event4xi5testx
ξ »lpu2image4xix
ξ »lpu2image4xi5testx
ξ »lpu2kernel4xix
ξ »lpu2kernel4xi5testx
ξ »lpu2program4xix
ξ »lpu2program4xi5testx
ξ »lpu2sampler4xix
ξ »lpu2sampler4xi5testx
ξ »lpu3image4xix
ξ »lpu3image4xi5testx
ξ »version4xix

compiled: > l2c

[m] special: None
ξ »mpu2buffer4xix
ξ »mpu2commandqueue4xix
ξ »mpu2commandqueue4xi5testx
ξ »mpu2context4xix
ξ »mpu2device4xix
ξ »mpu2dummy4xi5testx
ξ »mpu2event4xix
ξ »mpu2event4xi5testx
ξ »mpu2image4xix
ξ »mpu2image4xi5testx
ξ »mpu2kernel4xix
ξ »mpu2kernel4xi5testx
ξ »mpu2program4xix
ξ »mpu2program4xi5testx
ξ »mpu2sampler4xix
ξ »mpu2sampler4xi5testx
ξ »mpu3image4xix
ξ »mpu3image4xi5testx
ξ »version4xix

compiled: > m2c

[n] special: None
ξ »npu2buffer4xix
ξ »npu2commandqueue4xix
ξ »npu2commandqueue4xi5testx
ξ »npu2context4xix
ξ »npu2device4xix
ξ »npu2dummy4xi5testx
ξ »npu2event4xix
ξ »npu2event4xi5testx
ξ »npu2image4xix
ξ »npu2image4xi5testx
ξ »npu2kernel4xix
ξ »npu2kernel4xi5testx
ξ »npu2program4xix
ξ »npu2program4xi5testx
ξ »npu2sampler4xix
ξ »npu2sampler4xi5testx
ξ »npu3image4xix
ξ »npu3image4xi5testx
ξ »version4xix

compiled: > n2c

[o] special: None
ξ »opu2buffer4xix
ξ »opu2commandqueue4xix
ξ »opu2commandqueue4xi5testx
ξ »opu2context4xix
ξ »opu2device4xix
ξ »opu2dummy4xi5testx
ξ »opu2event4xix
ξ »opu2event4xi5testx
ξ »opu2image4xix
ξ »opu2image4xi5testx
ξ »opu2kernel4xix
ξ »opu2kernel4xi5testx
ξ »opu2program4xix
ξ »opu2program4xi5testx
ξ »opu2sampler4xix
ξ »opu2sampler4xi5testx
ξ »opu3image4xix
ξ »opu3image4xi5testx
ξ »version4xix

compiled: > o2c

[p] special: platformids4xi, program4xi
ξ »platformids4xix
ξ »platformids4xi5testx
ξ »platforminfo4xix
ξ »platforminfo4xi5testx
ξ »ppu2buffer4xix
ξ »ppu2commandqueue4xix
ξ »ppu2commandqueue4xi5testx
ξ »ppu2context4xix
ξ »ppu2device4xix
ξ »ppu2dummy4xi5testx
ξ »ppu2event4xix
ξ »ppu2event4xi5testx
ξ »ppu2image4xix
ξ »ppu2image4xi5testx
ξ »ppu2kernel4xix
ξ »ppu2kernel4xi5testx
ξ »ppu2program4xix
ξ »ppu2program4xi5testx
ξ »ppu2sampler4xix
ξ »ppu2sampler4xi5testx
ξ »ppu3image4xix
ξ »ppu3image4xi5testx
ξ »program4xix
ξ »program4xi5testx
ξ »version4xix

compiled: > p2c

[q] special: None
ξ »qpu2buffer4xix
ξ »qpu2commandqueue4xix
ξ »qpu2commandqueue4xi5testx
ξ »qpu2context4xix
ξ »qpu2device4xix
ξ »qpu2dummy4xi5testx
ξ »qpu2event4xix
ξ »qpu2event4xi5testx
ξ »qpu2image4xix
ξ »qpu2image4xi5testx
ξ »qpu2kernel4xix
ξ »qpu2kernel4xi5testx
ξ »qpu2program4xix
ξ »qpu2program4xi5testx
ξ »qpu2sampler4xix
ξ »qpu2sampler4xi5testx
ξ »qpu3image4xix
ξ »qpu3image4xi5testx
ξ »version4xix

compiled: > q2c

[r] special: None
ξ »rpu2buffer4xix
ξ »rpu2commandqueue4xix
ξ »rpu2commandqueue4xi5testx
ξ »rpu2context4xix
ξ »rpu2device4xix
ξ »rpu2dummy4xi5testx
ξ »rpu2event4xix
ξ »rpu2event4xi5testx
ξ »rpu2image4xix
ξ »rpu2image4xi5testx
ξ »rpu2kernel4xix
ξ »rpu2kernel4xi5testx
ξ »rpu2program4xix
ξ »rpu2program4xi5testx
ξ »rpu2sampler4xix
ξ »rpu2sampler4xi5testx
ξ »rpu3image4xix
ξ »rpu3image4xi5testx
ξ »version4xix

compiled: > r2c

[s] special: sampler4xi
ξ »sampler4xix
ξ »sampler4xi5testx
ξ »spu2buffer4xix
ξ »spu2commandqueue4xix
ξ »spu2commandqueue4xi5testx
ξ »spu2context4xix
ξ »spu2device4xix
ξ »spu2dummy4xi5testx
ξ »spu2event4xix
ξ »spu2event4xi5testx
ξ »spu2image4xix
ξ »spu2image4xi5testx
ξ »spu2kernel4xix
ξ »spu2kernel4xi5testx
ξ »spu2program4xix
ξ »spu2program4xi5testx
ξ »spu2sampler4xix
ξ »spu2sampler4xi5testx
ξ »spu3image4xix
ξ »spu3image4xi5testx
ξ »version4xix

compiled: > s2c

[t] special: None
ξ »tpu2buffer4xix
ξ »tpu2commandqueue4xix
ξ »tpu2commandqueue4xi5testx
ξ »tpu2context4xix
ξ »tpu2device4xix
ξ »tpu2dummy4xi5testx
ξ »tpu2event4xix
ξ »tpu2event4xi5testx
ξ »tpu2image4xix
ξ »tpu2image4xi5testx
ξ »tpu2kernel4xix
ξ »tpu2kernel4xi5testx
ξ »tpu2program4xix
ξ »tpu2program4xi5testx
ξ »tpu2sampler4xix
ξ »tpu2sampler4xi5testx
ξ »tpu3image4xix
ξ »tpu3image4xi5testx
ξ »version4xix

compiled: > t2c

[u] special: None
ξ »upu2buffer4xix
ξ »upu2commandqueue4xix
ξ »upu2commandqueue4xi5testx
ξ »upu2context4xix
ξ »upu2device4xix
ξ »upu2dummy4xi5testx
ξ »upu2event4xix
ξ »upu2event4xi5testx
ξ »upu2image4xix
ξ »upu2image4xi5testx
ξ »upu2kernel4xix
ξ »upu2kernel4xi5testx
ξ »upu2program4xix
ξ »upu2program4xi5testx
ξ »upu2sampler4xix
ξ »upu2sampler4xi5testx
ξ »upu3image4xix
ξ »upu3image4xi5testx
ξ »version4xix

compiled: > u2c

[v] special: None
ξ »version4xix
ξ »vpu2buffer4xix
ξ »vpu2commandqueue4xix
ξ »vpu2commandqueue4xi5testx
ξ »vpu2context4xix
ξ »vpu2device4xix
ξ »vpu2dummy4xi5testx
ξ »vpu2event4xix
ξ »vpu2event4xi5testx
ξ »vpu2image4xix
ξ »vpu2image4xi5testx
ξ »vpu2kernel4xix
ξ »vpu2kernel4xi5testx
ξ »vpu2program4xix
ξ »vpu2program4xi5testx
ξ »vpu2sampler4xix
ξ »vpu2sampler4xi5testx
ξ »vpu3image4xix
ξ »vpu3image4xi5testx

compiled: > v2c

[w] special: None
ξ »version4xix
ξ »wpu2buffer4xix
ξ »wpu2commandqueue4xix
ξ »wpu2commandqueue4xi5testx
ξ »wpu2context4xix
ξ »wpu2device4xix
ξ »wpu2dummy4xi5testx
ξ »wpu2event4xix
ξ »wpu2event4xi5testx
ξ »wpu2image4xix
ξ »wpu2image4xi5testx
ξ »wpu2kernel4xix
ξ »wpu2kernel4xi5testx
ξ »wpu2program4xix
ξ »wpu2program4xi5testx
ξ »wpu2sampler4xix
ξ »wpu2sampler4xi5testx
ξ »wpu3image4xix
ξ »wpu3image4xi5testx

compiled: > w2c

[x] special: None
ξ »version4xix
ξ »xpu2buffer4xix
ξ »xpu2commandqueue4xix
ξ »xpu2commandqueue4xi5testx
ξ »xpu2context4xix
ξ »xpu2device4xix
ξ »xpu2dummy4xi5testx
ξ »xpu2event4xix
ξ »xpu2event4xi5testx
ξ »xpu2image4xix
ξ »xpu2image4xi5testx
ξ »xpu2kernel4xix
ξ »xpu2kernel4xi5testx
ξ »xpu2program4xix
ξ »xpu2program4xi5testx
ξ »xpu2sampler4xix
ξ »xpu2sampler4xi5testx
ξ »xpu3image4xix
ξ »xpu3image4xi5testx

compiled: > x2c

[y] special: yoke4xi
ξ »version4xix
ξ »yoke4xix
ξ »ypu2buffer4xix
ξ »ypu2commandqueue4xix
ξ »ypu2commandqueue4xi5testx
ξ »ypu2context4xix
ξ »ypu2device4xix
ξ »ypu2dummy4xi5testx
ξ »ypu2event4xix
ξ »ypu2event4xi5testx
ξ »ypu2image4xix
ξ »ypu2image4xi5testx
ξ »ypu2kernel4xix
ξ »ypu2kernel4xi5testx
ξ »ypu2program4xix
ξ »ypu2program4xi5testx
ξ »ypu2sampler4xix
ξ »ypu2sampler4xi5testx
ξ »ypu3image4xix
ξ »ypu3image4xi5testx

compiled: > y2c

[z] special: z2skeleton4xi, zapimport2ball4xi
ξ »version4xix
ξ »z2skeleton4xix
ξ »z2skeleton4xi5testx
ξ »zapimport2ball4xix
ξ »zpu2buffer4xix
ξ »zpu2commandqueue4xix
ξ »zpu2commandqueue4xi5testx
ξ »zpu2context4xix
ξ »zpu2device4xix
ξ »zpu2dummy4xi5testx
ξ »zpu2event4xix
ξ »zpu2event4xi5testx
ξ »zpu2image4xix
ξ »zpu2image4xi5testx
ξ »zpu2kernel4xix
ξ »zpu2kernel4xi5testx
ξ »zpu2program4xix
ξ »zpu2program4xi5testx
ξ »zpu2sampler4xix
ξ »zpu2sampler4xi5testx
ξ »zpu3image4xix
ξ »zpu3image4xi5testx

compiled: > z2c

[ALL]
ξ ack2all = True in find2py4scope.py
ξ OK

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ DragonXi

Dragon Concept

ξ »China Daily
ξ dragon is an auspicious creature in Chinese culture, and it is loved by everyone
ξ Dragon became a main design element in Western luxury brands at the start of 2012,
ξ as their wealthy Chinese customers prepare to celebrate the Year of the Dragon
ξ Vertu, a British-based luxury mobile-phone manufacture that is a division of Nokia OYJ,
ξ has launched three phones for the Year of Dragon, complete with hand-engraved dragons -
ξ a process that takes around 36 hours for each unit. The handsets cost about 100,000 yuan ($15,831).
ξ dragon means good fortune, power and success /CEO Rolls-Royce/
ξ The year of the dragon reminds us of our dynamism, our energy, our power to make a difference/UN Secretary-General Ban Ki-moon/

ξ Bruce Lee and Jackie Chan - two of the biggest kungfu stars of all time.
ξ Their Chinese names are literally Li Little Dragon and Becoming Dragon.

ξ It is the only zodiac animal that never existed in the real world.
ξ It is a composite of nine animals: the snake, camel, elk, deer, mussel, carp, eagle, tiger and ox

ξ Chinese have at least two interpretations - usually polar opposite - for every sign and phenomenon,
ξ partly to ensure they'll end on a propitious note in even the worst event
ξ the dragon can be magnificent or menacing - It's all in your eyes!

ξ Chinese people's obsession with the dragon can be traced back to two origins:
ξ One is agricultural, and the other is imperial.
ξ The first one bases the dragon on the snake. It is a kind of water snake that can fly.
ξ When there is a drought, the dragon would fly up to the sky and shower rainwater across the land.
ξ In this interpretation, the phoenix is responsible for generating wind.

ξ the Chinese mythology is much richer and more complicated than that
ξ It has created many different forms of the dragon - some for heaven, some for earth and some for the elements.

ξ The four mighty rivers in China are said to be dragons that were transformed into waterways.
ξ However, the dragon leader supposedly originated from Qiantang,
ξ the bay in what is today Zhejiang's provincial capital, Hangzhou.
ξ This may confirm the suspicion that the earliest dragon legend could be from the ancient Yue culture.
ξ Ancient people attributed the caprices of the weather to the dragon's mood swings.
ξ some would have cursed the dragon for bringing floods.

ξ But, overall, people seemed to be optimistic about the benign nature of this at best partially visible creature,
ξ so conceived because it flies through clouds at lightning speed.
ξ To a certain extent, he usurped it from the common people. While he wore the dragon robe on the dragon throne,
ξ a commoner would have been beheaded for stitching this symbol on his rags.

ξ A dragon, compared for example to tiger, is beyond human reach!

ξ Snow Dragon, Xuelong in Chinese
ξ Vice-Premier Li Keqiang extended festival greetings to Chinese scientists working in the polar regions ahead of China's Lunar New Year
ξ during a visit to the National Marine Environmental Forecasting Center,
ξ Li made phone calls to scientists stationed in the polar regions and
ξ researchers aboard the scientific research vessel Snow Dragon,
ξ which is in the middle of a six-month Antarctic expedition
ξ Li called for efforts to increase the depth and scope of China's scientific research in both polar regions and oceans
ξ China should efficiently raise its capacity in exploring, protecting and comprehensively managing
ξ its oceanic territory, as required by the country's 12th Five-year Plan (2011-15)
ξ to explore and protect China's oceans is an inevitable strategic choice as the country pursues all-round opening up
ξ Li also stressed the need to protect China's maritime rights and interests

MSNBC
ξ »MSNBC
ξ the Chinese consider themselves descendants of the dragon,
ξ the only mythic creature in the Chinese 12-animal ξ »Zodiac

Reuters
ξ »Blogs
ξ Xin nian kuai le! <-- Happy New Year!
ξ this year is not just any year � it�s the year of the dragon
ξ it�s the year to have a baby!
ξ apparently, a dragon year is a seriously good year to be born
ξ the Chinese horoscope says that Chinese Dragons (you could call them Dragon babies I suppose) lead a complicated life,
ξ but have beneath their stubborn exterior, a soft heart, and are born leaders
ξ good attributes you would have to say, especially when you consider other animals included on the list
ξ are a pig, a rat, an ox, monkey, snake and even a sheep
ξ even though its the only fictitious animal on that list, you would have to say, a dragon is pretty cool
ξ it breathes fire�..cmon, that�s cool!!

SM Homeworld celebrates Year of the Dragon
ξ »philstar.com
ξ The Dragon is a creature of myth and legend
ξ in ancient China, the celestial Dragon represents an emperor and power
ξ Today, it is the ultimate auspicious symbol signifying
ξ potent, benevolent power, wisdom, wealth, and happiness

ξ The Year of the Dragon is considered particularly auspicious for new businesses, marriage and children
ξ The Dragon is considered the mightiest of signs because it combines parts of different animals
ξ the head of an ox, the muzzle of a donkey, the eyes of a shrimp, horns of a deer,
ξ the body of a serpent covered with fish scales, and the feet of a phoenix

Jqakartha
ξ »Jakarta Post
ξ the Year of the Dragon is dubbed a good year for investments
ξ perfect moment to savor numerous delicacies, usually only served during the Lunar New Year festivities
ξ in Chinese culture, every food has its meaning
ξ fish, for instance, represents abundance or wealth throughout the year

Nike
ξ »nike-zoom-kd-iv-year-of-the-dragon-release-date
ξ
ξ

open.edu
ξ »open.edu
ξ Dragon = l�ng

Fox
ξ »dragons-breath
ξ 'The Dragon�s Breath' -- a smokin' rice cake snack
ξ chef Marcel Vigneron
ξ

Youtube
ξ »Dragon�s Breath Popcorn
ξ COOL!
ξ Molecular Gastronomy!

Myths#1
ξ »The Star
ξ guards a gem the size of a peafowl�s egg
ξ on moonlit nights, comes out from its lake and plays with it � tossing it gracefully into the air and chasing after it
ξ dragon would thrash its tail about
ξ in a fit of fury, raise a great storm, bringing floods and angry waters to the people below
ξ dragon myths have gripped the minds and souls of humankind for eons
ξ there are dragon reliefs on the blue-glazed Ishtar Gate of Babylon
ξ in China, a 7,000-year-old dragon-shaped jade sculpture was found in a Neolithic archaeological site
ξ Dragons are found on Chinese scrolls, imperial robes, pottery, tombs, temples,
ξ Egyptian hieroglyphs and the prows of Viking ships

ξ dragon appears in one form or another in all the ancient mythologies
ξ in the old world, Chinese, Egyptian, Semitic, Hellenic, Celtic and Germanic
ξ In the new world, the cultures of the Meso-Americas also had a myth of the Quetzalcoatl,
ξ the �Feathered Snake�, which is analogous to the dragons of the Asian, African and Western-European cultures

ξ Sumerian and Babylonian dragon myths, symbolising the creation of order out of chaos <-- dragonize!
ξ were the earliest to surface, with written records going back several thousand years BC
ξ myth was of a dragon � symbolising chaos � being defeated by a god, who thereafter proceeded to create the world
ξ dragon in question was vast, ferocious, had a scaly body, horns and claws

ξ Why dragons? And how did so many cultures in different regions around the world come to embrace the idea?
ξ humans seem to have an innate aversion to snakes,
ξ probably due in part to the fact that these reptiles were established long before the first humans appeared and were seen as a threat
ξ many depictions of dragons bear an uncanny resemblance to a serpent or snake
ξ dragon is always, at heart, a snake
ξ peoples all over the world have compounded animals together or added components to natural animals to come up with monsters,
ξ and that is how a snake becomes a dragon

ξ even the Inuit � who do not have reptiles - have a dragon-like reptilian monster

ξ from the Babylonian creation epic, Enuma Elish: Marduk, chief god of Babylon,
ξ with his thunderbolts destroys Tiamat the dragon of primeval chaos and
ξ used the pieces of her body to form the world

ξ Merchants and buyers ended up trading more than just goods; they brought with them stories from home
ξ it is not difficult to imagine these stories being embellished or merging with other stories over time

ξ In the Germanic world, in particular, the indigenous dragon myths were amalgamated with dragon-concepts
ξ found in the accounts of lives of the saints of the Christian church
ξ In Beowulf, the earliest Germanic epic, and The Saga Of The Volsungs,
ξ a later Norse prose mythical saga based on early materials,
ξ the dragons show influence from the classical Roman and Greek dragon myths
ξ which were in turn influenced by ancient Semitic, near-eastern and biblical dragon concepts
ξ the dragon-like creatures of Egyptian myths and in the most ancient sources in the Western European tradition
ξ do not have wings

ξ Modern depictions of dragons are often of the huge, majestic, fire-breathing kind,
ξ but in earlier times, some versions were said to be as small as a butterfly or a flea <-- small & smart!
ξ myths and legends of the indigenous North Americans seem not to have had a dragon myth analogous to that of
ξ the European and Asian traditions or of the Meso-Americans to the south

ξ Is it less of a dragon if, instead of vomiting fire, it spits ice or acid?
ξ Are seven-headed serpents considered dragons?
ξ And what of dragon-like creatures without limbs, or wings?

ξ It is almost universal that there are dragon myths,
ξ but these are distinct between America, the Far East and the Middle East
ξ there are still amazingly similar dragon myths across the Middle East �
ξ from India to Greece and everywhere in between

ξ there are many different depictions of dragons, in form, temperament and the role it plays

Chinese dragon
ξ yang (of the yin yang concept)
ξ long and scaly
ξ has a horned head, legs and wings
ξ is able to exert control over weather and water � such as rivers and waterfalls, storms and floods
ξ can manifest as a violent waterspout over a lake or sea
ξ is benevolent and wise, and worthy of worship
ξ benevolent disposition of water in the spring rains and the flow of life-giving rivers,
ξ as well as the sea as the source of life,
ξ made the dragons that watched over these things powerful, fearsome, but essentially not enemies with humankind
ξ this was associated especially in Asia with the benevolent rule of powerful emperors and kings, and
ξ the idea developed that these rulers were themselves like dragons, or could appear in the form of dragons

Europe
ξ is often portrayed as an aggressive beast, swooping in on innocent townspeople and preying on fair maidens
ξ hoards treasure in hard-to-reach underground dens and caverns
ξ where there are dragons, there are also usually knights and dragon slayers (who usually win the battle)
ξ in religious texts and folklore, is often said to be evil personified and not to be taken literally

Africa
ξ elephant blood was known to be cold
ξ when the heat of Ethiopia got too much for the dragon, it would ambush an elephant to suck its blood
ξ as the elephant died, it fell over and crushed the dragon to death
ξ so if you were a (brave) human, you could then leap out and extract the magic dragon-stone, dracontias,
ξ from the dying dragon�s head
ξ this would protect you against poison, but it had to be taken while the dragon was still alive

Today
ξ we continue to be captivated by dragons!
ξ the idea of the dragon as the most fierce enemy a human or divine hero
ξ can face seems to be deeply rooted in modern popular consciousness
ξ we still talk about a person �having dragons to slay�, or tame
ξ the visual imagery has evolved to such an extent that the flying, fire-breathing, reptilian dragon
ξ simply looks fascinating
ξ Fairy tales are more than true; not because they tell us that dragons exist,
ξ but because they tell us that dragons can be beaten
ξ and maybe that is sufficient to ensure the survival of dragons in the modern world

Suomeksi(Finnish)
ξ »Imatralla aloitetaan lohikaarrmeen vuosi
ξ voimakkaan ja rohkean lohikaarrmeen vuosi alkaa 23. tammikuuta

Juhlaraha
ξ »Juhlaraha
ξ Lohikaarmett� pidet��n kiinalaiskulttuurissa vahvuuden symbolina.
ξ Se on aina edustanut keisarillista valtaa ja sen myota my�s suojelua.
ξ Nykypaivan� lohikaarme symboloi onnea ja menestysta
ξ Ajankohtaisia lohik��rmerahoja on ly�ty vain 8 888 kappaletta � koko maailmassa!
ξ lyontimaara viittaa kiinalaiseen onnennumeroon (8)
ξ Kiinalaisen kalenterin Lohikaarmeen vuosi kaynnistyy helmikuussa 2012
ξ aiemmat lohikaarmeen vuodet ovat olleet vuosina 1916, 1928, 1940, 1952, 1964, 1976, 1988 ja 2000

mahjongdragon.com
ξ »mahjongdragon.com
ξ keltainen lohikaarme on lohikaarmeiden kuningas <-- aurinko !
ξ jota on itse asiassa neljaa ja joka hallitsee itaa, etelaa, lantta ja pohjoista <-- suunnat
ξ

Ajatuksia
ξ keltainen (alkuperaisen punaset sense,reason,ace sateet ok)
ξ pieni ja alykas
ξ on puolellasi eika suinkaan vihollinen !
ξ tuo onnea, mihin yhdistyy numero 8 - ace it!
ξ modernimpi dragon voisi olla sunkin ystava(friend) - eika pelkastaan hallitsijoiden
ξ leikkisa - tarun mukaan tulee kuutamolla leikkimaan otsassa muuten olevalla jalokivella
ξ ei pelkaa lunta eika jaatakaan - onhan eskimoidenkin tarustossa lohikaarme
ξ on maapallonkin ystava - ekolohikaarme!

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ Forums

Forums

AMD

Δ »AMD Developer Forum
ξ login: dragonxi4amd
ξ password: amd4dragonxi

NVidia

ξ »NVidia Developer Zone
ξ login: dragonxi4nvidia
ξ password: L3tM3!in

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~ BLOG

BLOG

»Multiprocessing4Xi

»Studio4Xi

»Status2scope4Xi

March 29, 2015
ξ »shoot2dragon4uri.py
ξ »shoot2dragon4uri5test.py
ξ »automate2ref4uri.py
ξ verified URIs by using Studio4Xi services

April 7, 2014
ξ checked »version4xi.py
ξ compiled all »compile
ξ verified by studio4xi that temporary folders are being used in platform independent way in scope4xi
April 6, 2014
ξ Windows 8.1 Enterprise Evalution Buil 9600
ξ changed go3scope4fb.bat autoexec4scope.bat, version2scope4xi.bat and version4xi.py
ξ run all2core.bat to veridy core OpenCl modules!

December 9, 2013
ξ completed documentation!

December 7, 2013
ξ »#001 »#002 »#003
ξ updated documentation and made bacth files more independent of workstations

December 6, 2013
ξ hyperlinks of this documents checked using Studio4Xi

November 29, 2013
ξ parsed programs, compiled and run tests to all modules, took monthly backups

June 2, 2013
ξ monthly backups
ξ »3D-Image Objects for {BPU ... GPU ... ZPU}
ξ generated 3D image object modules with their tests in Studio4Xi to processing unit {BPU ... GPU ... ZPU} and tested in Scope4Xi

June 1, 2013
ξ backup Scope4Xi to V: and USB(H:)- FTP upload plus backup ROOT2TEMP4SCOPE: to V:
ξ »2D-Image Objects for {BPU ... GPU ... ZPU}
ξ generated 2D image object modules with their tests in Studio4Xi to processing unit {BPU ... GPU ... ZPU} and tested in Scope4Xi

May 31, 2013
ξ backup Scope4Xi to L: and USB(H:)- FTP upload plus backup ROOT2TEMP4SCOPE: to D:
ξ »Kernel Objects for {BPU ... GPU ... ZPU}
ξ generated kernel object modules with their tests in Studio4Xi to processing unit {BPU ... GPU ... ZPU} and tested in Scope4Xi

May 30, 2013
ξ backup Scope4Xi to F: and USB(H:)- FTP upload plus backup ROOT2TEMP4SCOPE: to D:
ξ »Sampler Objects for {BPU ... GPU ... ZPU}
ξ generated sampler object modules with their tests in Studio4Xi to processing unit {BPU ... GPU ... ZPU} and tested in Scope4Xi

May 29, 2013
ξ backup Scope4Xi to D: and USB(H:)- FTP upload plus backup ROOT2TEMP4SCOPE: to D:
ξ »Event Objects for {BPU ... GPU ... ZPU}
ξ generated event object modules with their tests in Studio4Xi to processing unit {BPU ... GPU ... ZPU} and tested in Scope4Xi

May 28, 2013
ξ backup Scope4Xi to V: and USB(H:)- FTP upload plus backup ROOT2TEMP4SCOPE: to V:
ξ »Command Queue Objects for {BPU ... GPU ... ZPU}
ξ generated command queue object modules with their tests in Studio4Xi to processing unit {BPU ... GPU ... ZPU} and tested in Scope4Xi

May 27, 2013
ξ backup Scope4Xi to F: and USB(H:)- FTP upload plus backup ROOT2TEMP4SCOPE: to F:
ξ »Device Objects for {BPU ... GPU ... ZPU}
ξ generated device object modules in Studio4Xi to processing unit {BPU ... GPU ... ZPU} and tested in Scope4Xi

May 26, 2013
ξ backup Scope4Xi to F: and USB(H:)- FTP upload plus backup ROOT2TEMP4SCOPE: to D:
ξ »Context Objects for {BPU ... GPU ... ZPU}
ξ generated context object modules in Studio4Xi to processing unit {BPU ... GPU ... ZPU} and tested in Scope4Xi

May 24, 2013
ξ backup Scope4Xi to D: and USB(H:)- FTP upload plus backup ROOT2TEMP4SCOPE: to D:
ξ »Buffer Objects for {BPU ... GPU ... ZPU}
ξ generated buffer object modules in Studio4Xi to processing unit {BPU ... GPU ... ZPU} and tested in Scope4Xi

May 23, 2013
ξ backup Scope4Xi to V and USB(H:)- FTP upload plus backup ROOT2TEMP4SCOPE: to V
ξ »Program Objects for {BPU ... GPU ... ZPU}
ξ generated program object modules in Studio4Xi to processing unit {BPU ... GPU ... ZPU} and tested in Scope4Xi

May 22, 2013
ξ backup to F and USB(H:)- FTP upload
ξ »Program Objects for {BPU ... GPU ... ZPU}
ξ updated instructions and generated source programs to handle program objects for real processing units
ξ completed steps (1) - (8)
ξ upgraded status of all modules so that status info is defined only once and in the beginning of each module
ξ »API-core sources
ξ collected links to API-modules

May 21, 2013
ξ backup to D and USB(H:)- FTP upload
ξ »Dragon processing unit
ξ checked API i.e. functions, classes and their methods
ξ parsed Scope4Xi modules in Studio4Xi
============================================================================================================================================
(Step 33A/33) OF PARSE2SCOPE4XI PARSED TOTALLY 36 TAGS IN : 314 MODULES 07:18:51 05/21/13 Pacific Daylight Time
(Step 33B/33) OF PARSE2SCOPE4XI + OK PARSING ..//..//..//..//..// scope4xi//041711//zap//lib// MODULES 07:18:51 05/21/13 Pacific Daylight Time
(Step 33C/33) OF PARSE2SCOPE4XI + OK EXPLORING FOLDER ..//..//..//..//..// scope4xi//041711//zap//lib// 07:18:51 05/21/13 Pacific Daylight Time
============================================================================================================================================

May 20, 2013
ξ backup to V and USB(H:)- FTP upload
ξ created HTML-files from zapped multiprocessing4xi XML-files »import2ball4xi
ξ upgraded go2scope-command to automatically copy /v/version4xi.py to other folders /a .../dragon ... /z
ξ defined dragon-subfolder in environment settings

May 19, 2013
ξ backup to F and USB(H:)- FTP upload
ξ »Compiling and testing
ξ updated copyright information

May 16, 2013
ξ setup environment in another workstation for Scope4Xi »Environment
ξ backup to D and USB(H:)- FTP upload
ξ »Xi device
ξ review

May 15, 2013
ξ setup environment in another workstation for Scope4Xi »Environment
ξ backup to D and USB(H:)- FTP upload
ξ »Special programs
ξ review tags

May 14, 2013
ξ backup to V and USB(H:)- FTP upload
ξ »Xi device
ξ updated trace mechanism in the modules designed for Xi = {APU ... GPU ... ZPU} device and corresponding the OpenCL API specifications!

May 13, 2013
ξ backup to F and USB(H:)- FTP upload
ξ »Dragon processing unit
ξ reviewed tags in all modules
ξ programmed »dragon2sampler4xi5test.py

May 12, 2013
ξ backup to D and USB(H:)- FTP upload
ξ »Dragon processing unit
ξ update for new dragon programs »Trace »Pickling »Actors »Nouns
ξ started testing dragon2event4xi5test.py, dragon2commandqueue4xi5test.py, dragon2kernel4xi5test.py
ξ completed first tests for dragon modules with trace
ξ updated APU device test modules trace settings to corresponding to those of dragon modules which are based on patterns used in multiprocessing test modules

May 11, 2013
ξ backup to V and USB(H:)- FTP upload
ξ »Dragon processing unit
ξ models to generate programs for other devices - NOT Xi={APU ... ZPU}
ξ created test programs dragon2event4xi5test.py, dragon2commandqueue4xi5test.py, dragon2kernel4xi5test.py

May 8, 2013
ξ backup to F and USB(H:)- FTP upload
ξ »Dragon processing unit
ξ replace pass in import trials with error message

May 7, 2013
ξ backup to D and USB(H:)- FTP upload
ξ took into use status2scope4xi.html
ξ »Dragon processing unit
ξ created dragon2buffer4xi.py, dragon2commandqueue4xi.py, dragon2context4xi.py, dragon2device4xi.py, dragon2event4xi.py
ξ updated version4xi.py with 'dragon' key

May 6, 2013
ξ backup to V and USB(H:)- FTP upload
ξ »Walktrough and Overview
ξ »Generating code automatically

May 5, 2013
ξ backup to L and USB(H:)- FTP upload
ξ completed »Conversion to 041721
ξ all folders examines - this was because some contain special modules not specific to any processing unit
ξ parsed all modules »#065

May 4, 2013
ξ backup to F and USB(H:)- no FTP upload
ξ continue to study how scope4xi works and how to generate programs to other devices

May 3, 2013
ξ backup to F and USB(H:)- no FTP upload
ξ studied how scope4xi works and how to generate programs to other devices
ξ »Parsing
ξ parse2scope4xi.py

ξ »Fetching Scope Programs
ξ is this necessary anymore?

ξ »Building Scope Programs
ξ due to bug in Python marshal operation fails - one must wait until the guys get this bug fixed !

ξ »Fetch2url4scope
ξ programmed to test fetching Python source files from Web portal for create2kernel4apu.py in scope4xi - fails

ξ »Version
ξ this module is definetely needed to keep updated!

ξ »Find
ξ find2py4scope.py - needed!

ξ »Dragonizing
ξ examples how to generate image programs to other devices using APU image program
ξ how about other programs ?

ξ »Generating Image Programs for Devices
ξ instructions how to generate, deploy and test image programs to other devices using APU image program
ξ how about other programs ?
ξ »Deployment to Scope4Xi
ξ instructions how to deploy image programs
ξ how about other programs ?

May 2, 2013
ξ backup to D and USB(H:)- no FTP upload
ξ »Studio4Xi
ξ »Multiprocessing4Xi
ξ compiled and run all using the new Python 3.3 Release 17.21
ξ run4xi: python commandqueue4xi5test.py > ..\..\work\txt\commandqueue4xi5test.txt
ξ all2c.bat OK - the only difference to older Python 3.2. are warnings about failed .del commands which are typical to the new Python version!
ξ populated index.html to be able to directly FTP upload to server
ξ discovered that *5test*.p? and thereby the master and generator have to be changed to refer to the new version 041721 and python33

October 9, 2012
ξ »Studio4Xi
ξ »Multiprocessing4Xi
ξ »version4xi
ξ upgraded to Python 3.3 in all directories _ a ... z
ξ »commandqueue4xi5test.py
ξ »pipe4xi.py
ξ openmode2xi = win32.PIPE_ACCESS_INBOUND - global name win32 is not defined
ξ all2c OK except the above which uses the new multiprocessing4xi module which was not yet converted

October 1, 2012
ξ »Studio4Xi
ξ »Multiprocessing4Xi
ξ reviewed with above

April 23, 2012
ξ re-compiled
ξ backep up

March 9, 2012
ξ »apu2buffer4xi.py
ξ explored how Python code could be saved and described for search engine at web portal
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ »apu2kernel4xi5test.txt
ξ started class tests
ξ execute2nativekernel4apu functions checks if 'CODE4KERNEL' in keys2kernel4apu:
ξ updated public API of apu2kernel4xi.py by referring to specification APU in public API interface documentation

January 24, 2012
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ execution function with arguments - explored whether tester could set arguments and provide target function

January 23, 2012
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ programmed execute function to activare process with target function without arguments
ξ changed links to relative for web usage
ξ moved job to /web/temp/job because /web exists at yourdragonxi.dom
ξ however, one can work using Studio4Xi so that it uses different local drive than where web contents are!

January 19, 2012
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ added automatic parameter building into execute2kernel4apu function

January 18, 2012
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ programmed and tested execute2kernel4apu function in prototype level without parameters

January 17, 2012
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ completed set2kernelarg4apu and made it simple to use

January 16, 2012
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ completed get2kernelinfo4apu, set2kernel4apu, release2kernel4apu, retain2kernel4apu, trace2kernel4apu, set2kernelcallback4apu

January 12, 2012
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ COUNT2SOURCE processing programmed and tested with create and add functions

January 11, 2012
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ CODE4BIN, CODE4C, CODE4CL, CODE4CPP, CODE4PY and CODE4PYC - each having one or more programs
ξ COUNT4BIN, COUNT4C, COUNT4CL, COUNT4CPP, COUNT4PY and COUNT4PYC - are these necessary ?
ξ SIZE4BIN, SIZE4C, SIZE4CL, SIZE4CPP, SIZE4PY and SIZE4PYC - are these actually counters of corresponsing dictionaries?
ξ upgraded create, add and delete functions to handle above attributes !

January 10, 2012
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ programmed and tested both delete2kernel4apu and add2kernel4apu functions

January 5, 2012
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ programmed add2kernel4apu function to handle .exe and .c types

January 3, 2012
ξ »kernel4xi.py
ξ »kernel4xi5test.py
ξ continued testing kernel module for virtual device Xi »#024
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ hit errors in master kernel module apu2kernel4xi.py and its test module apu2kernel4xi5test.py !
ξ had to go back to test master kernel modules - unfortunately this means regenerating cycle later on !
ξ programmed add2kernel4apu function to handle new source types .cpp and .cl

January 2, 2012
ξ »kernel4xi.py
ξ »kernel4xi5test.py
ξ generated kernels to all processing units in Studio4Xi and programmed kernel module for virtual device Xi »#024

December 17, 2011
ξ »apu2kernel4xi.py
ξ »apu2program4xi.py
ξ updated embedded comments for parsing in Studio4Xi

December 15, 2011
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ programmed to create required data not given by caller and tested create2kernel4apu function call with task parameter

December 14, 2011
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ instead of just checking that binary exists for each source it fetches binary file, both Python .pyc and C++ .exe files
ξ tested fetching Python source from web page - authorization was denied, Python 3.3. had bugs »#033
ξ omitted so far the idea to fetch from web due to problems encountered (bugs in Python 3.3 ...) and to keep guarantee good response times

December 13, 2011
ξ »apu2kernel4xi.py
ξ .py, .pyc, .cpp and .exe file types handled
ξ »apu2kernel4xi5test.py
ξ create2kernel4apu function without giving parameters tested
ξ create2programwithsource4apu handled C++ type of source program apu2dummy4xi5test.cpp
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ programmed C++ default source to be generated because apu2kernel4xi.py needs it
ξ instead of using embedded dictionary considered to rely on tag if no parameters are given to create2kernel4apu function - abondeded the idea

December 12, 2011
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ Python kernels detected from Program object generated by create2programwithsource4apu function
ξ C++ kernels detected from fetched C++ input files - not from Program object because create2programwithsource4apu does not generate default C++ sources

December 09, 2011
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ created bin subfolder to a ... z and dragon folders
ξ programmed to handle .py, .c, .cpp, .cl and .pyc, .exe types of files

December 08, 2011
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ upgrading apu2kernel4xi.py to handle several program types (C++/Python) and extensions(.pyc/.exe) at the same time
ξ create2kernel4apu function under process to handle Python source files in more general way
ξ open input file - read mode set according to file type

December 07, 2011
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ create2kernel4xi function tested both with and without parameter, class object created, create2kernel method tested
ξ upgraded all create functions in all APU modules so that trial to create an attribute is done only if it is in keys of task (either passed or generated automatically)
ξ upgrade speeds create functions and reduces yielded messages in trace

December 06, 2011
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ started testing create2kernel4xi function

December 05, 2011
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ added kernel functions and class to trace in print4xi.py; updated pickle2?4xi.py and actor2?4xi.py modules »#024

December 04, 2011
ξ »apu2kernel4xi.py
ξ »apu2kernel4xi5test.py
ξ started programming kernel objects »#024

December 02, 2011
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ »#024
ξ both function and method upgraded to handle kernel object although based on program object models

November 30, 2011
ξ »program4xi.py
ξ »program4xi5test.py
ξ proprammed preparation for set function
ξ both functions and class with all methods tested for virtual XI = {APU ...ZPU}!

November 29, 2011
ξ »program4xi.py
ξ »program4xi5test.py
ξ proprammed focus to make testing easier
ξ up to focus 10 tested - set function is the next one!

November 28, 2011
ξ »WEB
ξ programmed build2scope4xi.py
ξ tests revealed bug in Python 3.3 : marshall loads failed - also p2exe in not supported
ξ we must wait Python 3.3. bug to get fixed and leave build function as it is
ξ that means program objects can be generated to all devices !

November 27, 2011
ξ »program4xi.py
ξ »program4xi5test.py
ξ both functions and class methods tested
ξ improved create program with binary and source - freedom to select focus randomly creates more challenges to functions and methods!

November 26, 2011
ξ »program4xi.py
ξ »program4xi5test.py
ξ focus 01...12 tested

November 25, 2011
ξ »program4xi.py
ξ »program4xi5test.py
ξ added possibility to select whichs tests are to be run while keeping the option to tune trace !
ξ tuned some functions to handle and return responses from device modules instead of common programxi
ξ succeeded to run the whole test - results to be analyzed and testing to be tuned
ξ to be tuned dragon trace and degug trace
ξ run c_all4xi & all2c and took weekly backups to all devices
ξ »zpu2program4xi.py
ξ »zpu2program4xi5test.py
ξ to be explored how to define subfolders a ...z in test program to help automatic software generation - //lib//a// problem in

November 24, 2011
ξ »program4xi.py
ξ »program4xi5test.py
ξ programmed and started test program object for virtual device Xi

November 23, 2011
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ programmed and testing compile function specified in the new OpenCL specification version 1.2
ξ simulated compilitation and linking with Process4Xi operations
ξ developed functions to import the needed function from its module into program object !
ξ discovered that you have to perform tailor2trace4program(t2xi) again if the target function of activated process resets trace!
ξ generated program objects »Program Objects

November 22, 2011
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ programmed and tested methods add2programwithsource, add2programwithbinary, delete2programwithbinary' and delete2programwithsource

November 21, 2011
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ programmed and tested functions add2programwithsource4apu and add2programwithbinary4apu

November 18, 2011
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ tested build function
ξ updated pickle2?4xi.py and actor2?.py modules for all processing units ready for software generation

November 17, 2011
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ completed binary code tests
ξ considered delete function valid both for source and binary
ξ hit by the facto that Python does NOT build cache version from test programs!

November 16, 2011
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ completed source code tests

November 15, 2011
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ started first tests

November 14, 2011
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ continued programming of »Program Objects
ξ at AMD OpenCL Developer Forum chatted about memory objects

November 10, 2011
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ apu2program4xi.py programmed first version »Program Objects

November 10, 2011
ξ »apu2program4xi.py
ξ »apu2program4xi5test.py
ξ »Program Objects

November 9, 2011
ξ »sampler4xi.py
ξ »sampler4xi5test.py
ξ »Samplers

November 8, 2011
ξ »apu2sampler4xi.py
ξ »apu2sampler4xi5test.py
ξ tested to {apu ... zpu}

November 7, 2011
ξ »apu2sampler4xi.py
ξ »apu2sampler4xi5test.py
ξ started programming and testing »Sampler Objects
ξ updated »Actors »Picklers

November 6, 2011
ξ »image3d4xi.py
ξ »image3d4xi5test.py
ξ COMPLETED TESTING 2D and 3D IMAGE OPERATIONS FOR ALL PROCESSING UNITS!
ξ »image2d4xi.py
ξ »image2d4xi5test.py
ξ changed messaging so that sent messages such as roger are being echoed (if ok) by received

November 5, 2011
ξ »image3d4xi.py
ξ »image3d4xi5test.py
ξ programmed 3D image operations
ξ »image2d4xi.py
ξ »image2d4xi5test.py
ξ completed both function and class tests - 2D Image handling done to all processing units !
ξ negative resposnses still to be checked!

November 4, 2011
ξ »image2d4xi.py
ξ »image2d4xi5test.py
ξ unified queue and channel naming - queue and channel operations with wrong names is dangerous and put application to halt !
ξ queue4verb, where verb = {read,write,map ...}, for example queue4read
ξ channel4verb2publish, channel4verb2consumer - verb = {read, write,map ...}, for example channel4read2publish, channel4read2consumer

November 4, 2011
ξ »image2d4xi.py
ξ »image2d4xi5test.py
ξ other manoeuvres
ξ class methods to handle standard tunable task dictionary
ξ parameter usage and service walk trough
ξ xml generation

November 3, 2011
ξ »image2d4xi.py
ξ »image2d4xi5test.py
ξ succeeded to complete read operation with 2D images manoeuvring with APU, GPU, ZPU processing units at the same time!
ξ handling dictionaries with xi device is challenging compared to handling data with real devices!

November 2, 2011
ξ »image2d4xi.py
ξ »image2d4xi5test.py
ξ added focus to manoeuvre functions

November 1, 2011
ξ »image2d4xi.py
ξ »image2d4xi5test.py
ξ programmed possibility to select active processing unit(s) for a test

November 1, 2011
ξ »image2d4xi.py
ξ »image2d4xi5test.py
ξ compeleted programming 2D image processing for virtual processing unit xi
ξ started testing 2D image processing for virtual processing unit xi
ξ defined more trace to be able to continue critical parts

October 31, 2011
ξ »image2d4xi.py
ξ »image2d4xi5test.py
ξ continued programming 2D image processing for virtual processing unit xi
ξ make sure dictionaries such as queue2copy4xi get initialized!
ξ check whether finctions should check {} also !
ξ check queue and channel settings using read function as model !
ξ make sure to initialize response dictionary - see read function!
ξ do NOT change dictionary from {} to None for individual device modules - check in xi module before it calls device module
ξ most functions such as trace do not pass any arguments anyhow whereas create needs !
ξ make sure to use individual PU messages and data because they show the history and are being shown by trace!

October 31, 2011
ξ »image2d4xi.py
ξ programmed more virtual device xi (APU ... ZPU) handling, which is powerful but also demanding !
ξ decided to keep multiple data with multiple functions to quarantee re-entrancy, speed and concurrent usage of up to 26 processing units for 2D images
ξ unresolved whether COUNT2REFERENCE is set when image objects are created !!
ξ solved why XPU data was different to others - XPU device was missing in keys2pu
ξ trace became too large - have to tailor and check pickling modules pickle2?4xi.py and print4xi.py!
ξ rule of thumb: when calling Xi device function you give and receive dictionaries
ξ rule of thumb: when sendind and receiving messages or putting and getting you loop all devices

October 30, 2011
ξ »image2d4xi.py
ξ »image2d4xi5test.py
ξ converted 2D image handling for xi (virtual all) device - create and set done, get2imageinfo4xi returned too much

October 28, 2011
ξ »image2d4xi.py
ξ »buffer4xi.py
ξ started to modify image2d4xi.py to handle several devices using buffer4xi.py as model

ξ »image3d4xi5test.py
ξ »image3d4xi.py
ξ tested 3D images for xi device - not yet handling selected devices with version4xi.py - but instead xi as a device
ξ »image2d4xi5test.py
ξ »image2d4xi.py
ξ tested 2D images for xi device - not yet handling selected devices with version4xi.py - but instead xi as a device
ξ »image2d4xi.py
ξ hit the problem can not import create2event4xi »Unresolved
ξ from event4xi import create2event4xi succeeded in the same folder e with event4xi.py !
ξ from event4xi import create2event4xi succeeded when event4xi.py was in the same folder i with image2d4xi.py !
ξ import event4xi <-- OK!
ξ from event4xi import Event4Xi <-- OK!

ξ programmed 2D image modules for virtual device xi »2D image modules
ξ programmed 3D image modules for virtual device xi »3D image modules

October 27, 2011
ξ 3D image processing modules and image test modules generated automatically to all devices
ξ »bpu3image4xi.py
...
ξ »zpu3image4xi.py
ξ deployed by Studio4Xi »WEB4Xi

October 21, 2011
ξ 2D image processing modules generated automatically to all devices
ξ »bpu2image4xi.py
...
ξ »zpu2image4xi.py
ξ deployed by Studio4Xi »WEB4Xi

October 12, 2011
ξ created »WEB4Xi

October 10, 2011
ξ »apu2image4xi.py
ξ »apu2image4xi5test.py
ξ verified usage documentation and tested 2D image operations both with functions and class methods
ξ »parsed all source programs
ξ documented solution alternatives for state machines to handle 2D and 3D image operations »State Machine or Thread

October 9, 2011
ξ »apu3image4xi.py
ξ »apu3image4xi5test.py
ξ tested 3D image operations
ξ »print4xi.py
ξ added trace for 3D image operations
ξ decided to have different trace for 2D and 3D image operations, although it makes print4xi.py much larger!
ξ hit with set functions to the fact that you (caller) have to take into account the attributes such as pitch which depend on other attributes such as width, height and depth!

October 6, 2011
ξ »apu3image4xi.py
ξ apu2image4xi.py as start, defines APU3Image4Xi class
ξ »apu3image4xi5test.py
ξ tests 3D image operations, uses APU3Image4Xi class
ξ »apu2image4xi.py
ξ tested 2D and 3D
ξ »apu2image4xi5test.py
ξ tests mostly 2D image operations - some 3D - kept as it is so far (changed would mean new testing!)
ξ upgraded to print keys and corresponding values of response to clarify test results
ξ »print4xi.py
ξ added APU3Image4Xi class to be traced

October 5, 2011
ξ »apu2image4xi.py
ξ embedded trace to each function and method thereby also verfying the correctness of the code
ξ »apu2image4xi5test.py
ξ tested all once again to verify the latest changes in functions and methods
ξ dictionary eventwaitlistquantity2apu['QUANTITY'] = the number of elements in the dictionary eventwaitlist2apu
ξ considered whether to program 3D image module or in Studio4Xi the one generating 2D image processing to other processing units!
ξ reviewed the logic how to handle given parameters
ξ if no task parameter dictionary from caller, try to provide them and then continue checking them because it allows you to check that you provided all parameters
ξ note that you could skip checking the task disctionary provided by program but you would loose the test possibility and double checking feature!
ξ if task parameter dictionary has been provided by caller, check it and try to provide missing ones
ξ create function always have to try to create and to yield if a feature has not been given by user or provided by program itself

October 4, 2011
ξ »apu2image4xi5test.py
ξ tested copy2imagetobuffer, copybuffer2image and map image functions and methods
ξ »apu2image4xi.py
ξ programmed copy2imagetobuffer, copybuffer2image and map2image functions and methods and corresponding manoeuvre functions

October 3, 2011
ξ »apu2image4xi5test.py
ξ tested write2image, read2image and copy2imagemethods
ξ tested write2image4apu, read2image4apu and copy2image4apu functions
ξ tested manoeuvre2readimage4apu, manoeuvre2writeimage4apu and manoeuvre2copyimage4apu functions
ξ »apu2image4xi.py
ξ programmed write2image, read2image and copy2image methods
ξ programmed manoeuvre2readimage4apu, manoeuvre2writeimage4apu and manoeuvre2copyimage4apu, functions
ξ upgraded read and manoeuvre functions to be independent
ξ »print4xi.py
ξ added manoeuvre and copy functions to be traced

September 30, 2011
ξ »apu2image4xi5test.py
ξ test command & control and 2D image file operation with thread
ξ »apu2image4xi.py
ξ activate dummy process in read2image4apu function
ξ explore whether target function can return anything and whether it should return once all states completed !

September 29, 2011
ξ »apu2image4xi5test.py
ξ tested command & control and 2D image file operation with simulation
ξ »apu2image4xi.py
ξ manoeuvre2image4apu function command and control and image path info programmed as state machine
ξ pipe is used to send and receive command and control:
ξ (1) copy2read4apu; (2) roger2read4apu; (3) ready2read4apu; (1) ack2imageinfo4apu
ξ queue is used to put and get data: (4) ..//..//..//..//..//web//images//png//dragonxi.png
ξ once data has been processed command and control about operation is sent and received (5) ack2imageinfo4apu

September 28, 2011
ξ »print4xi.py
ξ added manoeuvre functions
ξ »apu2image4xi5test.py
ξ test command & control and 2D image file operation by simulating thread
ξ »apu2image4xi.py
ξ programmed new function manoeuvre2image4apu to handle command & control
ξ activates dummy process with the above new function

September 27, 2011
ξ »apu2image4xi5test.py
ξ programmed and tested simulating command & control and 2D image file operation
ξ »programs used as models for communication

September 17, 2011
ξ »Nouns4Xi - Model for Command & Control
ξ explored as model for command & control

September 11, 2011
ξ explore command and control with (send and receive), (put and get) or invent command and control (copy,roger) (ack,nack)

September 10, 2011
ξ »apu2image4xi.py
ξ programmed get2imageinfo4apu function so that it also returns only requested elements and their values
ξ »apu2image4xi5test.py
ξ tested by getting only height and width of 2D image

September 9, 2011
ξ »apu2image4xi.py
ξ started to program read function for 2D images
ξ programmed parameter providing for both cases - missing totally or some required parameters missing
ξ established consumer and publisher channels for control and command messages between caller
ξ »apu2image4xi5test.py
ξ got response with queue and pipe channels

September 8, 2011
ξ »apu3image4xi.py
ξ »apu3image4xi5test.py
ξ programmed depth attribute for 3D images of APU device, started read function for 2D images of APU
ξ parsed and checked possible failures using Studio4Xi
ξ »queue4xi.py
ξ »queue_arena4xi.py
ξ programmed queue tests with image files - concluded that queue requires ASCII data
ξ you can put and get file paths and messages but you can NOT put and get image files !

September 7, 2011
ξ »apu3image4xi.py
ξ »apu3image4xi5test.py
ξ tested - create and set only with 2D values
ξ »arena4xi.py
ξ »test_arena4xi.py
ξ explored Arena4Xi objects, memory maps and mapping images - not supported enough for Scope4Xi in Python !
ξ many Python libraries such as Image and PNG don't support the latest Python compiler

ξ »apu2image4xi.py
ξ »apu2image4xi5test.py
ξ programmed more functions and methods such as get2supportedimageformats4apu function get2supportedimageformats method
ξ revealed the weakeness of current OpenCL specifications - you need a separate function to get detailed object data
ξ realized the benefit of dragonized OpenCL - you can access any object data by using its element name such as FORMAT for images

September 6, 2011
ξ »print4xi.py
ξ added rest of image trace
ξ run image tests with existing create, started testing set

September 5, 2011
ξ decided to program own modules for 2D and 3D images
ξ »apu2image4xi.py
ξ »apu2image4xi5test.py
ξ 2D image object processing
ξ »apu3image4xi.py
ξ »apu3image4xi5test.py
ξ 3D image object processing
ξ »print4xi.py
ξ more trace

September 2, 2011
ξ »apu2image4xi.py
ξ programmed create function for image object for APU
ξ »apu2image4xi5test.py
ξ tested create, release, retain functions and class methods
ξ »print4xi.py
ξ added APU ... ZPU image classes to trace

ξ »buffer4xi.py
ξ »buffer4xi5test.py
ξ »apu2buffer4xi.py
ξ »bpu2buffer4xi.py
ξ »cpu2buffer4xi.py
ξ »dpu2buffer4xi.py
ξ »epu2buffer4xi.py
ξ »fpu2buffer4xi.py
ξ »gpu2buffer4xi.py
ξ »hpu2buffer4xi.py
ξ »ipu2buffer4xi.py
ξ »jpu2buffer4xi.py
ξ »kpu2buffer4xi.py
ξ »lpu2buffer4xi.py
ξ »mpu2buffer4xi.py
ξ »npu2buffer4xi.py
ξ »opu2buffer4xi.py
ξ »ppu2buffer4xi.py
ξ »qpu2buffer4xi.py
ξ »rpu2buffer4xi.py
ξ »spu2buffer4xi.py
ξ »tpu2buffer4xi.py
ξ »upu2buffer4xi.py
ξ »vpu2buffer4xi.py
ξ »xpu2buffer4xi.py
ξ »wpu2buffer4xi.py
ξ »ypu2buffer4xi.py
ξ »zpu2buffer4xi.py
ξ pointer to buffer changed to memory map i.e. buffer attribute of Arena4Xi object

September 1, 2011
ξ »apu2image4xi.py
ξ image object for APU
ξ »apu2device4xi.py
ξ explored how to handle image support - AMD does not support 2D and 3D images for devices, not even to CPU!
ξ »New Module Development
ξ used image object for APU as an example

August 30, 2011
ξ class trace must be checked with ALL tests!
ξ »event4xi.py
ξ »event4xi5test.py
ξ device events absolute
ξ »event4xi.py
ξ »event4xi5test.py
ξ device events relative

August 29, 2011
ξ »apu2event4xi.py
ξ »bpu2event4xi.py
ξ »cpu2event4xi.py
ξ »dpu2event4xi.py
ξ »epu2event4xi.py
ξ »fpu2event4xi.py
ξ »gpu2event4xi.py
ξ »hpu2event4xi.py
ξ »ipu2event4xi.py
ξ »jpu2event4xi.py
ξ »kpu2event4xi.py
ξ »lpu2event4xi.py
ξ »mpu2event4xi.py
ξ »npu2event4xi.py
ξ »opu2event4xi.py
ξ »ppu2event4xi.py
ξ »qpu2event4xi.py
ξ »rpu2event4xi.py
ξ »spu2event4xi.py
ξ »tpu2event4xi.py
ξ »upu2event4xi.py
ξ »vpu2event4xi.py
ξ »xpu2event4xi.py
ξ »wpu2event4xi.py
ξ »ypu2event4xi.py
ξ »zpu2event4xi.py
ξ event for each device
ξ »apu2event4xi5test.py
ξ »bpu2event4xi5test.py
ξ »cpu2event4xi5test.py
ξ »dpu2event4xi5test.py
ξ »epu2event4xi5test.py
ξ »fpu2event4xi5test.py
ξ »gpu2event4xi5test.py
ξ »hpu2event4xi5test.py
ξ »ipu2event4xi5test.py
ξ »jpu2event4xi5test.py
ξ »kpu2event4xi5test.py
ξ »lpu2event4xi5test.py
ξ »mpu2event4xi5test.py
ξ »npu2event4xi5test.py
ξ »opu2event4xi5test.py
ξ »ppu2event4xi5test.py
ξ »qpu2event4xi5test.py
ξ »rpu2event4xi5test.py
ξ »spu2event4xi5test.py
ξ »tpu2event4xi5test.py
ξ »upu2event4xi5test.py
ξ »vpu2event4xi5test.py
ξ »xpu2event4xi5test.py
ξ »wpu2event4xi5test.py
ξ »ypu2event4xi5test.py
ξ »zpu2event4xi5test.py
ξ tests for each device
ξ improved trace and wait functions, checked dragonized trace for all methods and functions
ξ »find2text4scope.py
ξ »print4xi.py
ξ solved 1) why wait is not printed in trace 2) updated functions init_xxx_print_objects4xi, where xxx = a ...z

August 26, 2011
ξ »event4xi5test.py
ξ event tested with XI processor, which is actually knowledgebase (dictionary) containing events for all devices APU ... ZPU

August 25, 2011
ξ »event4xi.py
ξ events to XI processor

August 24, 2011
ξ »apu2event4xi.py
ξ »bpu2event4xi.py
ξ »cpu2event4xi.py
ξ »dpu2event4xi.py
ξ »epu2event4xi.py
ξ »fpu2event4xi.py
ξ »gpu2event4xi.py
ξ »hpu2event4xi.py
ξ »ipu2event4xi.py
ξ »jpu2event4xi.py
ξ »kpu2event4xi.py
ξ »lpu2event4xi.py
ξ »mpu2event4xi.py
ξ »npu2event4xi.py
ξ »opu2event4xi.py
ξ »ppu2event4xi.py
ξ »qpu2event4xi.py
ξ »rpu2event4xi.py
ξ »spu2event4xi.py
ξ »tpu2event4xi.py
ξ »upu2event4xi.py
ξ »vpu2event4xi.py
ξ »xpu2event4xi.py
ξ »wpu2event4xi.py
ξ »ypu2event4xi.py
ξ »zpu2event4xi.py
ξ event for each device
ξ »apu2event4xi5test.py
ξ »bpu2event4xi5test.py
ξ »cpu2event4xi5test.py
ξ »dpu2event4xi5test.py
ξ »epu2event4xi5test.py
ξ »fpu2event4xi5test.py
ξ »gpu2event4xi5test.py
ξ »hpu2event4xi5test.py
ξ »ipu2event4xi5test.py
ξ »jpu2event4xi5test.py
ξ »kpu2event4xi5test.py
ξ »lpu2event4xi5test.py
ξ »mpu2event4xi5test.py
ξ »npu2event4xi5test.py
ξ »opu2event4xi5test.py
ξ »ppu2event4xi5test.py
ξ »qpu2event4xi5test.py
ξ »rpu2event4xi5test.py
ξ »spu2event4xi5test.py
ξ »tpu2event4xi5test.py
ξ »upu2event4xi5test.py
ξ »vpu2event4xi5test.py
ξ »xpu2event4xi5test.py
ξ »wpu2event4xi5test.py
ξ »ypu2event4xi5test.py
ξ »zpu2event4xi5test.py
ξ tests for each device

ξ »apu2commandqueue4xi.py
ξ task4create2apu ['PROPERTIES'] = None <=> can be used to assume that profiling is enabled and commands executed out-of-order

August 15, 2011
ξ »apu2event4xi.py
ξ »apu2event4xi5test.py
ξ tested apu2event4xi.py

ξ »TIPS of Multiprocessing4Xi
ξ updated the tip for testing that all trace messages are ok in system
ξ »print4xi.py
ξ added trace for release and retain

August 15, 2011
ξ »apu2event4xi.py
ξ programming event for APU device
ξ »apu2event4xi5test.py
ξ programming and started test for apu2event4xi.py
ξ »print4xi.py
ξ updated trace and statistics for events - to all devices
ξ »actor2a4xi.py
ξ updated events such as APU2Event4Xi - to all
ξ »pickle2a4xi.py
ξ updated picklers such as APU2Event4Xi - to all

August 12, 2011
ξ used Studio4Xi to a) parse b) find errors, warnings, exceptions in Scope4Xi

ξ »find2py4scope.py
ξ ../../../lib/-/> ROOT2STUDIO4TXT:/find2py4scope.txt

ξ »find2text4scope.py
ξ ../../../wor/\/xt\ --> ROOT2STUDIO4TXT:/find2text4scope.txt

ξ »version4xi.py
ξ knowledgebase updated for the above two modules
ξ »Studio4Xi for Scope4Xi

ξ »buffer4xi.py
ξ »buffer4xi5test.py
ξ warned instead of failed if optional data

ξ »import2ball4xi.py
ξ »zapimport2ball4xi.py

ξ »parse2scope4xi
ξ ../../../lib/-/> ../../../txt/parse2scope4xi.txt

ξ »commandqueue4xi.py
ξ added flush and finish - operated on all devices APU ... ZPU
ξ »commandqueue4xi5test.py
ξ tested flush and finish on all devices APU ... ZPU

August 11, 2011
ξ »apu2commandqueue4xi.py
ξ »bpu2commandqueue4xi.py
ξ »cpu2commandqueue4xi.py
ξ »dpu2commandqueue4xi.py
ξ »epu2commandqueue4xi.py
ξ »fpu2commandqueue4xi.py
ξ »gpu2commandqueue4xi.py
ξ »hpu2commandqueue4xi.py
ξ »ipu2commandqueue4xi.py
ξ »jpu2commandqueue4xi.py
ξ »kpu2commandqueue4xi.py
ξ »lpu2commandqueue4xi.py
ξ »mpu2commandqueue4xi.py
ξ »npu2commandqueue4xi.py
ξ »opu2commandqueue4xi.py
ξ »ppu2commandqueue4xi.py
ξ »qpu2commandqueue4xi.py
ξ »rpu2commandqueue4xi.py
ξ »spu2commandqueue4xi.py
ξ »tpu2commandqueue4xi.py
ξ »upu2commandqueue4xi.py
ξ »vpu2commandqueue4xi.py
ξ »xpu2commandqueue4xi.py
ξ »wpu2commandqueue4xi.py
ξ »ypu2commandqueue4xi.py
ξ »zpu2commandqueue4xi.py
ξ programmed flush and finish functions and methods to commandqueues

ξ »apu2commandqueue4xi5test.py
ξ »bpu2commandqueue4xi5test.py
ξ »cpu2commandqueue4xi5test.py
ξ »dpu2commandqueue4xi5test.py
ξ »epu2commandqueue4xi5test.py
ξ »fpu2commandqueue4xi5test.py
ξ »gpu2commandqueue4xi5test.py
ξ »hpu2commandqueue4xi5test.py
ξ »ipu2commandqueue4xi5test.py
ξ »jpu2commandqueue4xi5test.py
ξ »kpu2commandqueue4xi5test.py
ξ »lpu2commandqueue4xi5test.py
ξ »mpu2commandqueue4xi5test.py
ξ »npu2commandqueue4xi5test.py
ξ »opu2commandqueue4xi5test.py
ξ »ppu2commandqueue4xi5test.py
ξ »qpu2commandqueue4xi5test.py
ξ »rpu2commandqueue4xi5test.py
ξ »spu2commandqueue4xi5test.py
ξ »tpu2commandqueue4xi5test.py
ξ »upu2commandqueue4xi5test.py
ξ »vpu2commandqueue4xi5test.py
ξ »xpu2commandqueue4xi5test.py
ξ »wpu2commandqueue4xi5test.py
ξ »ypu2commandqueue4xi5test.py
ξ »zpu2commandqueue4xi5test.py
ξ programmed flush and finish functions and methods to commandqueues

ξ »queue4xi.py
ξ added trace and used some new methods such as empty, full and state for commandqueues
ξ »print4xi.py
ξ added trace

August 10, 2011
ξ programmed command queues for all devices!
ξ »apu2commandqueue4xi.py
ξ »bpu2commandqueue4xi.py
ξ »cpu2commandqueue4xi.py
ξ »dpu2commandqueue4xi.py
ξ »epu2commandqueue4xi.py
ξ »fpu2commandqueue4xi.py
ξ »gpu2commandqueue4xi.py
ξ »hpu2commandqueue4xi.py
ξ »ipu2commandqueue4xi.py
ξ »jpu2commandqueue4xi.py
ξ »kpu2commandqueue4xi.py
ξ »lpu2commandqueue4xi.py
ξ »mpu2commandqueue4xi.py
ξ »npu2commandqueue4xi.py
ξ »opu2commandqueue4xi.py
ξ »ppu2commandqueue4xi.py
ξ »qpu2commandqueue4xi.py
ξ »rpu2commandqueue4xi.py
ξ »spu2commandqueue4xi.py
ξ »tpu2commandqueue4xi.py
ξ »upu2commandqueue4xi.py
ξ »vpu2commandqueue4xi.py
ξ »xpu2commandqueue4xi.py
ξ »wpu2commandqueue4xi.py
ξ »ypu2commandqueue4xi.py
ξ »zpu2commandqueue4xi.py
ξ tested command queues for all devices!
ξ »apu2commandqueue4xi5test.py
ξ »bpu2commandqueue4xi5test.py
ξ »cpu2commandqueue4xi5test.py
ξ »dpu2commandqueue4xi5test.py
ξ »epu2commandqueue4xi5test.py
ξ »fpu2commandqueue4xi5test.py
ξ »gpu2commandqueue4xi5test.py
ξ »hpu2commandqueue4xi5test.py
ξ »ipu2commandqueue4xi5test.py
ξ »jpu2commandqueue4xi5test.py
ξ »kpu2commandqueue4xi5test.py
ξ »lpu2commandqueue4xi5test.py
ξ »mpu2commandqueue4xi5test.py
ξ »npu2commandqueue4xi5test.py
ξ »opu2commandqueue4xi5test.py
ξ »ppu2commandqueue4xi5test.py
ξ »qpu2commandqueue4xi5test.py
ξ »rpu2commandqueue4xi5test.py
ξ »spu2commandqueue4xi5test.py
ξ »tpu2commandqueue4xi5test.py
ξ »upu2commandqueue4xi5test.py
ξ »vpu2commandqueue4xi5test.py
ξ »xpu2commandqueue4xi5test.py
ξ »wpu2commandqueue4xi5test.py
ξ »ypu2commandqueue4xi5test.py
ξ »zpu2commandqueue4xi5test.py

ξ »SENSE »REASON ξ »ACE XML and ξ »Test Files!

ξ »commandqueue4xi.py
ξ »commandqueue4xi5test.py
ξ tests command queues for all devices - creating one demanding trace file for editor and one big XML file for browser

August 9, 2011
ξ »print4xi.py
ξ updated trace and statistics for OpenCL modules to include modules to all devices
ξ »bpu2commandqueue4xi.py
ξ »bpu2commandqueue4xi5test.py
ξ continued testing - create method and function tested - Pipe4Xi and Queue4Xi objects tested with functions and methods

August 8, 2011
ξ added Pipe4Xi object to command queues with all processing units
ξ used core_count4xi function to set class variable
ξ »commandqueue4xi.py
ξ »commandqueue4xi5test.py
ξ tests all devices - might create too big a trace file, if trace is not minimized
ξ »apu2commandqueue4xi.py
ξ »bpu2commandqueue4xi.py
ξ »bpu2commandqueue4xi5test.py
ξ programmed test program for bpu2commandqueue4xi.py
ξ »cpu2commandqueue4xi.py
ξ »dpu2commandqueue4xi.py
ξ »epu2commandqueue4xi.py
ξ »fpu2commandqueue4xi.py
ξ »gpu2commandqueue4xi.py
ξ »hpu2commandqueue4xi.py
ξ »ipu2commandqueue4xi.py
ξ »jpu2commandqueue4xi.py
ξ »kpu2commandqueue4xi.py
ξ »lpu2commandqueue4xi.py
ξ »mpu2commandqueue4xi.py
ξ »npu2commandqueue4xi.py
ξ »opu2commandqueue4xi.py
ξ »ppu2commandqueue4xi.py
ξ »qpu2commandqueue4xi.py
ξ »rpu2commandqueue4xi.py
ξ »spu2commandqueue4xi.py
ξ »tpu2commandqueue4xi.py
ξ »upu2commandqueue4xi.py
ξ »vpu2commandqueue4xi.py
ξ »xpu2commandqueue4xi.py
ξ »wpu2commandqueue4xi.py
ξ »ypu2commandqueue4xi.py
ξ »zpu2commandqueue4xi.py

June 14, 2011
ξ added Queue4Xi object to command queues with all processing units
ξ »commandqueue4xi.py
ξ »commandqueue4xi5test.py
ξ »apu2commandqueue4xi.py
ξ »bpu2commandqueue4xi.py
ξ »cpu2commandqueue4xi.py
ξ »dpu2commandqueue4xi.py
ξ »epu2commandqueue4xi.py
ξ »fpu2commandqueue4xi.py
ξ »gpu2commandqueue4xi.py
ξ »hpu2commandqueue4xi.py
ξ »ipu2commandqueue4xi.py
ξ »jpu2commandqueue4xi.py
ξ »kpu2commandqueue4xi.py
ξ »lpu2commandqueue4xi.py
ξ »mpu2commandqueue4xi.py
ξ »npu2commandqueue4xi.py
ξ »opu2commandqueue4xi.py
ξ »ppu2commandqueue4xi.py
ξ »qpu2commandqueue4xi.py
ξ »rpu2commandqueue4xi.py
ξ »spu2commandqueue4xi.py
ξ »tpu2commandqueue4xi.py
ξ »upu2commandqueue4xi.py
ξ »vpu2commandqueue4xi.py
ξ »xpu2commandqueue4xi.py
ξ »wpu2commandqueue4xi.py
ξ »ypu2commandqueue4xi.py
ξ »zpu2commandqueue4xi.py

June 8, 2011
ξ »parse2scope4xi.py
ξ »parse2scope4xi.txt
============================================================================================================================================
(STEP 33A/33) OF PARSE2SCOPE4XI PARSED TOTALLY 36 TAGS IN : 141 MODULES 19:47:16 06/07/11 Pacific Daylight Time
(STEP 33B/33) OF PARSE2SCOPE4XI + OK PARSING ..//..//..//..//..// scope4xi//041721//zap//lib// MODULES 19:47:16 06/07/11 Pacific Daylight Time
(STEP 33C/33) OF PARSE2SCOPE4XI + OK EXPLORING FOLDER ..//..//..//..//..// scope4xi//041721//zap//lib// 19:47:16 06/07/11 Pacific Daylight Time
============================================================================================================================================

ξ tested command queues with all processing units
ξ »commandqueue4xi.py
ξ »commandqueue4xi5test.py
ξ »apu2commandqueue4xi.py
ξ »bpu2commandqueue4xi.py
ξ »cpu2commandqueue4xi.py
ξ »dpu2commandqueue4xi.py
ξ »epu2commandqueue4xi.py
ξ »fpu2commandqueue4xi.py
ξ »gpu2commandqueue4xi.py
ξ »hpu2commandqueue4xi.py
ξ »ipu2commandqueue4xi.py
ξ »jpu2commandqueue4xi.py
ξ »kpu2commandqueue4xi.py
ξ »lpu2commandqueue4xi.py
ξ »mpu2commandqueue4xi.py
ξ »npu2commandqueue4xi.py
ξ »opu2commandqueue4xi.py
ξ »ppu2commandqueue4xi.py
ξ »qpu2commandqueue4xi.py
ξ »rpu2commandqueue4xi.py
ξ »spu2commandqueue4xi.py
ξ »tpu2commandqueue4xi.py
ξ »upu2commandqueue4xi.py
ξ »vpu2commandqueue4xi.py
ξ »xpu2commandqueue4xi.py
ξ »wpu2commandqueue4xi.py
ξ »ypu2commandqueue4xi.py
ξ »zpu2commandqueue4xi.py

June 7, 2011
ξ »buffer4xi.py
ξ »buffer4xi5test.py
ξ »apu2buffer4xi.py
ξ »bpu2buffer4xi.py
ξ »cpu2buffer4xi.py
ξ »dpu2buffer4xi.py
ξ »epu2buffer4xi.py
ξ »fpu2buffer4xi.py
ξ »gpu2buffer4xi.py
ξ »hpu2buffer4xi.py
ξ »ipu2buffer4xi.py
ξ »jpu2buffer4xi.py
ξ »kpu2buffer4xi.py
ξ »lpu2buffer4xi.py
ξ »mpu2buffer4xi.py
ξ »npu2buffer4xi.py
ξ »opu2buffer4xi.py
ξ »ppu2buffer4xi.py
ξ »qpu2buffer4xi.py
ξ »rpu2buffer4xi.py
ξ »spu2buffer4xi.py
ξ »tpu2buffer4xi.py
ξ »upu2buffer4xi.py
ξ »vpu2buffer4xi.py
ξ »xpu2buffer4xi.py
ξ »wpu2buffer4xi.py
ξ »ypu2buffer4xi.py
ξ »zpu2buffer4xi.py
ξ tested buffers for all processing units

June 6, 2011
ξ »context4xi.py
ξ »context4xi5test.py
ξ »apu2context4xi.py
ξ »bpu2context4xi.py
ξ »cpu2context4xi.py
ξ »dpu2context4xi.py
ξ »epu2context4xi.py
ξ »fpu2context4xi.py
ξ »gpu2context4xi.py
ξ »hpu2context4xi.py
ξ »ipu2context4xi.py
ξ »jpu2context4xi.py
ξ »kpu2context4xi.py
ξ »lpu2context4xi.py
ξ »mpu2context4xi.py
ξ »npu2context4xi.py
ξ »opu2context4xi.py
ξ »ppu2context4xi.py
ξ »qpu2context4xi.py
ξ »rpu2context4xi.py
ξ »spu2context4xi.py
ξ »tpu2context4xi.py
ξ »upu2context4xi.py
ξ »vpu2context4xi.py
ξ »xpu2context4xi.py
ξ »wpu2context4xi.py
ξ »ypu2context4xi.py
ξ »zpu2context4xi.py
ξ tested context for all processing units

June 5, 2011
ξ »device4xi.py
ξ »device4xi5test.py
ξ [ ] A - [X] »apu2device4xi.py
ξ [ ] B - [*] »bpu2device4xi.py
ξ [ ] C - [X] »cpu2device4xi.py
ξ [ ] D - [X] »dpu2device4xi.py
ξ [ ] E - [*] »epu2device4xi.py
ξ [ ] F - [*] »fpu2device4xi.py
ξ [ ] G - [X] »gpu2device4xi.py
ξ [ ] H - [*] »hpu2device4xi.py
ξ [ ] I - [*] »ipu2device4xi.py
ξ [ ] J - [*] »jpu2device4xi.py
ξ [ ] K - [*] »kpu2device4xi.py
ξ [ ] L - [*] »lpu2device4xi.py
ξ [ ] M - [*] »mpu2device4xi.py
ξ [ ] N - [?] »npu2device4xi.py
ξ [ ] O - [*] »opu2device4xi.py
ξ [ ] P - [X] »ppu2device4xi.py
ξ [ ] Q - [*] »qpu2device4xi.py
ξ [ ] R - [X] »rpu2device4xi.py
ξ [ ] S - [X] »spu2device4xi.py
ξ [ ] T - [*] »tpu2device4xi.py
ξ [ ] U - [*] »upu2device4xi.py
ξ [ ] V - [X] »vpu2device4xi.py
ξ [ ] W - [*] »xpu2device4xi.py
ξ [ ] X - [*] »wpu2device4xi.py
ξ [ ] Y - [*] »ypu2device4xi.py
ξ [ ] Z - [*] »zpu2device4xi.py
ξ tests for all processing units

June 4, 2011
ξ »actor2c4xi.py
ξ »actor2g4xi.py
ξ »actor2s4xi.py
ξ actors for all devices and create actor for context, command queue, buffer and subbuffer
ξ »pickle2t4xi.py
ξ trace
ξ »pickle2c4xi.py
ξ create
ξ »pickle2s4xi.py
ξ set
ξ »pickle2g4xi.py
ξ get
ξ »pickle2r4xi.py
ξ release and retain
ξ »pickle2i4xi.py
ξ init
ξ »print4xi.py
ξ trace
ξ »actor2c4xi.py
ξ added create-actor to context, command queue, buffer and subbuffer

June 3, 2011
ξ »print4xi.py
ξ dragonized trace for new modules

June 2, 2011
ξ »pickle2a4xi.py
ξ »pickle2b4xi.py
ξ »pickle2c4xi.py
ξ »pickle2d4xi.py
ξ »pickle2e4xi.py
ξ »pickle2f4xi.py
ξ »pickle2g4xi.py
ξ »pickle2h4xi.py
ξ »pickle2i4xi.py
ξ »pickle2j4xi.py
ξ »pickle2k4xi.py
ξ »pickle2l4xi.py
ξ »pickle2m4xi.py
ξ »pickle2n4xi.py
ξ »pickle2o4xi.py
ξ »pickle2p4xi.py
ξ »pickle2q4xi.py
ξ »pickle2r4xi.py
ξ »pickle2s4xi.py
ξ »pickle2t4xi.py
ξ »pickle2u4xi.py
ξ »pickle2v4xi.py
ξ »pickle2w4xi.py
ξ »pickle2x4xi.py
ξ »pickle2y4xi.py
ξ »pickle2z4xi.py
ξ added pickling for new modules - class plus create, get and set functions
ξ »actor2a4xi.py
ξ »actor2b4xi.py
ξ »actor2c4xi.py
ξ »actor2d4xi.py
ξ »actor2e4xi.py
ξ »actor2f4xi.py
ξ »actor2g4xi.py
ξ »actor2h4xi.py
ξ »actor2i4xi.py
ξ »actor2j4xi.py
ξ »actor2k4xi.py
ξ »actor2l4xi.py
ξ »actor2m4xi.py
ξ »actor2n4xi.py
ξ »actor2o4xi.py
ξ »actor2p4xi.py
ξ »actor2q4xi.py
ξ »actor2r4xi.py
ξ »actor2s4xi.py
ξ »actor2t4xi.py
ξ »actor2u4xi.py
ξ »actor2v4xi.py
ξ »actor2w4xi.py
ξ »actor2x4xi.py
ξ »actor2y4xi.py
ξ »actor2z4xi.py
ξ added new actors
ξ »parse2scope4xi.py
ξ »parse2scope4xi.txt
ξ parsing

May 26 - 29, 2011
ξ explored new objects: the rest of the OpenCL objects + scope objects + zeta objects + series + processing units + general nouns + special nouns
ξ [ ] A - [ ] ace [ ] act [ ] action [ ] aframe [ ] alpha [ ] aperture [ ] arc [ ] assets
ξ [ ] B - [ ] bpu [ ] balance [ ] barrier [ ] base [ ] beat [ ] beta [ ] bpu [ ] build [ ] burst
ξ [ ] C - [ ] camera [ ] cast [ ] cell [ ] charge [ ] checkpoint [ ] core [ ] cue [ ] cutback
ξ [ ] D - [ ] defense [ ] delivery [ ] delta [ ] deployment [ ] direction [ ] distance [ ] dragon [ ] dude
ξ [ ] E - [ ] epu [ ] ecosystem [ ] energy [ ] engine [ ] environment [ ] epsilon [ ] event [ ] exposure
ξ [ ] F - [ ] fpu [ ] field [ ] fire [ ] flow [ ] focus [ ] force [ ] front [ ] fusion
ξ [ ] G - [ ] gage [ ] game [ ] gamma [ ] gap [ ] goal [ ] grid [ ] group [ ] gun
ξ [ ] H - [ ] hpu [ ] hatch [ ] head [ ] health [ ] hit [ ] hide [ ] hold [ ] hollow
ξ [ ] I - [ ] ipu [ ] identication [ ] igniter [ ] image [ ] incide [ ] infiltration [ ] intelligence [ ] inspection [ ] issue
ξ [ ] J - [ ] jpu [ ] jack [ ] jib [ ] job [ ] joint [ ] joist [ ] judder [ ] junction
ξ [ ] K - [ ] kpu [ ] keg [ ] kernel [ ] kicker [ ] kickoff [ ] kink [ ] knowledge [ ] kyle
ξ [ ] L - [ ] lpu [ ] lambda [ ] layback [ ] layer [ ] lens [ ] lighting [ ] load [ ] lull
ξ [ ] M - [ ] mpu [ ] magazine [ ] maneuver [ ] mark [ ] math [ ] maverick [ ] memobject [ ] mission
ξ [ ] N - [ ] npu [ ] narration [ ] ndrange [ ] net [ ] normalize [ ] notify [ ] nose [ ] nuclear
ξ [ ] O - [ ] opu [ ] obstacle [ ] ocean [ ] Orchestra [ ] offshore [ ] operation [ ] origin [ ] overlay
ξ [ ] P - [ ] pace [ ] payload [ ] pipeline [ ] pitch [ ] pool [ ] power [ ] profile [ ] program
ξ [ ] Q - [ ] qpu [ ] qualifier [ ] quality [ ] guiver [ ] quince [ ] quipu [ ] query [ ] quiz
ξ [ ] R - [ ] rail [ ] ray [ ] reasoner [ ] receiver [ ] render [ ] resource [ ] rip [ ] router
ξ [ ] S - [ ] sampler [ ] scene [ ] scope [ ] sensor [ ] script [ ] sphere [ ] source [ ] shadow
ξ [ ] T - [ ] tpu [ ] target [ ] task [ ] talent [ ] texture [ ] theater [ ] tone [ ] turtle
ξ [ ] U - [ ] upu [ ] union [ ] unload [ ] unmap [ ] ubity [ ] underexposure [ ] upas [ ] usage
ξ [ ] V - [ ] vector [ ] vendor [ ] venerer [ ] venue [ ] video [ ] visibility [ ] voice [ ] voxel
ξ [ ] W - [ ] wpu [ ] waitlist [ ] wave [ ] wing [ ] wipeout [ ] workitem [ ] worklist [ ] workgroup
ξ [ ] X - [ ] xpu [ ] xenops [ ] xi [ ] xray [ ] xylem [ ] xyster [ ] xyston [ ] xystus
ξ [ ] Y - [ ] ypu [ ] yabba [ ] yacht [ ] yad [ ] yarn [ ] yielder [ ] yag [ ] yeast
ξ [ ] Z - [ ] zpu [ ] zabra [ ] zambra [ ] zanze [ ] zero [ ] zarf [ ] zeta [ ] zone

ξ »Space
ξ »Arts
ξ »Law
ξ »Wines
ξ »Science
ξ »Business
ξ »Photography
ξ »Green Living Tips
ξ »Fishing
ξ »Movie Terminology Glossary
ξ »Animation
ξ »Music
ξ »Opera LA
ξ »Dance & Theatre Terms
ξ »Snowboarding
ξ »Surfing Waves
ξ »Phrontistery
ξ »FAS Lexicon

May 25, 2011
ξ discovered clRetainMemObject and clReleaseMemObject functions
ξ clCreateBuffer, clCreateSubBuffer, and clCreateImage{2D|3D} perform an implicit retain
ξ after the memobj reference count becomes zero and commands queued for execution on a command-queue(s) that use memobj have finished, the memory object is deleted.
ξ If memobj is a buffer object, memobj cannot be deleted until all sub-buffer objects associated with memobj are deleted.

May 25, 2011
ξ programmed create function for sub-buffers so that reference count of corresponding buffer is added by one !
ξ reference count - decided to keep setting to zero when buffer is created, because the resource is being created - not used - and then retain can be called if taken into use!
ξ chatted in AMD forum - it looks like release and retain command are missing for sub-buffers - Scope4Xi allows to calculate i.e. to add and substract !
ξ it's programmers responsibility to manage buffers - which may be cached
ξ only when read and write commands are commanded via queue may buffers get released !

May 24, 2011
ξ »buffer4xi5test.py
ξ tested sub-buffers for all devices

May 23, 2011
ξ »buffer4xi5test.py
ξ the first test for buffers xi, apu ... vpu
ξ added xi, which acts as main device for OpenCL devices APU ... VPU, into trace
ξ create2buffer4xi, 4apu....4vpu tested
ξ »arena4xi.py
ξ used size attribute to test the size of each created Arena object !

May 22, 2011
ξ »buffer4xi5test.py
ξ »buffer4xi.py
ξ »buffer4xi5test.txt
ξ buffer main with tests
ξ »apu2buffer4xi.py
ξ »cpu2buffer4xi.py
ξ »dpu2buffer4xi.py
ξ »gpu2buffer4xi.py
ξ »ppu2buffer4xi.py
ξ »rpu2buffer4xi.py
ξ »spu2buffer4xi.py
ξ »vpu2buffer4xi.py
ξ buffer modules per device

ξ »pickle2a4xi.py - APU
ξ »pickle2b4xi.py - main
ξ »pickle2c4xi.py - CPU
ξ »pickle2d4xi.py - DPU
ξ »pickle2g4xi.py - GPU
ξ »pickle2p4xi.py - PPU
ξ »pickle2r4xi.py - RPU
ξ »pickle2s4xi.py - SPU
ξ »pickle2t4xi.py - TRACE
ξ »pickle2v4xi.py - VPU
ξ picklers for buffer modules

ξ »actor2a4xi.py - APU
ξ »actor2b4xi.py - main
ξ »actor2c4xi.py - CPU
ξ »actor2d4xi.py - DPU
ξ »actor2g4xi.py - GPU
ξ »actor2p4xi.py - PPU
ξ »actor2r4xi.py - RPU
ξ »actor2s4xi.py - SPU
ξ »actor2t4xi.py - TRACE
ξ »actor2v4xi.py - VPU
ξ actors for buffer modules

ξ »arena4xi.py
ξ provides memory arena to buffers
ξ »print4xi.py
ξ dragonized trace for buffer modules

ξ »parse2scope4xi.py
ξ »parse2scope4xi.txt
ξ parsing for all scope modules

May 20, 2011
ξ tested thoroughly and embedded trace into commandqueue4xi.py and apu2commandqueue4xi.py ... vpu2commandqueue4xi.py

May 19, 2011
ξ »commandqueue4xi5test.py
ξ »commandqueue4xi.py
ξ »commandqueue4xi5test.txt
ξ completed first command queue tests
ξ updated all get functions to handle non initialized data
ξ improved ack and nack steps trace visually

May 18, 2011
ξ »commandqueue4xi5test.py
ξ »commandqueue4xi.py
ξ »commandqueue4xi5test.txt
ξ started command queue tests

ξ »apu2commandqueue4xi.py
ξ »cpu2commandqueue4xi.py
ξ »dpu2commandqueue4xi.py
ξ »gpu2commandqueue4xi.py
ξ »ppu2commandqueue4xi.py
ξ »rpu2commandqueue4xi.py
ξ »spu2commandqueue4xi.py
ξ »vpu2commandqueue4xi.py
ξ command queue test, main and module per device - context modules used as models

ξ »pickle2a4xi.py - APU
ξ »pickle2c4xi.py - CPU
ξ »pickle2d4xi.py - DPU
ξ »pickle2g4xi.py - GPU
ξ »pickle2p4xi.py - PPU
ξ »pickle2r4xi.py - RPU
ξ »pickle2s4xi.py - SPU
ξ »pickle2t4xi.py - TRACE
ξ »pickle2v4xi.py - VPU
ξ picklers for command queue modules

ξ »actor2a4xi.py - APU
ξ »actor2c4xi.py - CPU
ξ »actor2d4xi.py - DPU
ξ »actor2g4xi.py - GPU
ξ »actor2p4xi.py - PPU
ξ »actor2r4xi.py - RPU
ξ »actor2s4xi.py - SPU
ξ »actor2t4xi.py - TRACE
ξ »actor2v4xi.py - VPU
ξ actors for command queue modules

ξ »print4xi.py
ξ dragonized trace for command queue modules

ξ »parse2scope4xi.py
ξ »parse2scope4xi.txt
============================================================================================================================================
(STEP 33A/33) OF PARSE2SCOPE4XI PARSED TOTALLY 36 TAGS IN : 60 MODULES 08:59:42 05/18/11 Pacific Daylight Time
(STEP 33B/33) OF PARSE2SCOPE4XI + OK PARSING ..//..//..//..//..// scope4xi//041721//zap//lib// MODULES 08:59:42 05/18/11 Pacific Daylight Time
(STEP 33C/33) OF PARSE2SCOPE4XI + OK EXPLORING FOLDER ..//..//..//..//..// scope4xi//041721//zap//lib// 08:59:42 05/18/11 Pacific Daylight Time
============================================================================================================================================

May 15, 2011
ξ »context4xi5test.py
ξ »context4xi.py
ξ tested main context and release and retain functions and methods
ξ »parse2scope4xi.py
ξ »parse2scope4xi.txt
============================================================================================================================================
(STEP 33A/33) OF PARSE2SCOPE4XI PARSED TOTALLY 36 TAGS IN : 51 MODULES 03:18:21 05/15/11 Pacific Daylight Time
(STEP 33B/33) OF PARSE2SCOPE4XI + OK PARSING ..//..//..//..//..// scope4xi//041721//zap//lib// MODULES 03:18:21 05/15/11 Pacific Daylight Time
(STEP 33C/33) OF PARSE2SCOPE4XI + OK EXPLORING FOLDER ..//..//..//..//..// scope4xi//041721//zap//lib// 03:18:21 05/15/11 Pacific Daylight Time
============================================================================================================================================

May 13, 2011
ξ »context4xi5test.py
ξ »context4xi.py
ξ »apu2context4xi.py
ξ »cpu2context4xi.py
ξ »dpu2context4xi.py
ξ »gpu2context4xi.py
ξ »ppu2context4xi.py
ξ »rpu2context4xi.py
ξ »spu2context4xi.py
ξ »vpu2context4xi.py
ξ release and retain for context programmed and tested !

May 12, 2011
ξ »context4xi5test.py
ξ tested context management with all eight(8) processing units
ξ tested simulated callback from an OpenCL device by redirecting callback of each device to print4xi.py

ξ »context4xi.py
ξ context management with all eight(8) processing units

ξ »context4xi5test.txt
ξ »apu2context4xi.py
ξ »cpu2context4xi.py
ξ »dpu2context4xi.py
ξ »gpu2context4xi.py
ξ »ppu2context4xi.py
ξ »rpu2context4xi.py
ξ »spu2context4xi.py
ξ »vpu2context4xi.py
ξ context management of a processing unit

ξ »print4xi.py
ξ dragonized trace - capable to receive and handle callbacks rerouted from OpenCL devices

ξ »actor2a4xi.py
ξ »actor2c4xi.py
ξ »actor2d4xi.py
ξ »actor2g4xi.py
ξ »actor2i4xi.py
ξ »actor2p4xi.py
ξ »actor2r4xi.py
ξ »actor2s4xi.py
ξ »actor2t4xi.py
ξ »actor2v4xi.py
ξ actors for context

ξ »pickle2a4xi.py
ξ »pickle2c4xi.py
ξ »pickle2d4xi.py
ξ »pickle2g4xi.py
ξ »pickle2i4xi.py
ξ »pickle2p4xi.py
ξ »pickle2r4xi.py
ξ »pickle2s4xi.py
ξ »pickle2t4xi.py
ξ »pickle2v4xi.py
ξ picklers for context

May 11, 2011
ξ »context4xi.py
ξ »context4xi5test.py
ξ »context4xi5test.txt
ξ completed dragonized trace definitions into pickle?4xi.py, print4xi.py and actor?4xi.py modules and started to analyze dragonized trace
ξ »HTML color codes
ξ defined individual colors for all new actors

May 10, 2011
ξ »context4xi.py
ξ »context4xi5test.py
ξ test to context of all (8) processing units: 'APU, ,CPU','DPU', 'GPU', PPU', 'RPU', SPU', 'VPU'
ξ »apu2context4xi.py
ξ »cpu2context4xi.py
ξ »dpu2context4xi.py
ξ »gpu2context4xi.py
ξ »ppu2context4xi.py
ξ »rpu2context4xi.py
ξ »spu2context4xi.py
ξ »vpu2context4xi.py
ξ context to all (8) processing units: 'APU, ,CPU','DPU', 'GPU', PPU', 'RPU', SPU', 'VPU'

May 9, 2011
ξ »context4xi.py
ξ »context4xi5test.py
ξ context to all (8) processing units: 'APU, ,CPU','DPU', 'GPU', PPU', 'RPU', SPU', 'VPU' ('apu, ,cpu','dpu', 'gpu', ppu', 'rpu', spu', 'vpu')
ξ »apu2context4xi.py
ξ »dpu2context4xi.py
ξ »ppu2context4xi.py
ξ »rpu2context4xi.py
ξ »spu2context4xi.py
ξ »vpu2context4xi.py
ξ 8 context - one for each processing unit: 'APU, ,CPU','DPU', 'GPU', PPU', 'RPU', SPU', 'VPU'
ξ »actor2a4xi.py
ξ »actor2c4xi.py
ξ »actor2d4xi.py
ξ »actor2g4xi.py
ξ »actor2p4xi.py
ξ »actor2r4xi.py
ξ »actor2s4xi.py
ξ »actor2t4xi.py
ξ »actor2v4xi.py
ξ actors for context
ξ »pickle2a4xi.py
ξ »pickle2c4xi.py
ξ »pickle2d4xi.py
ξ »pickle2g4xi.py
ξ »pickle2p4xi.py
ξ »pickle2r4xi.py
ξ »pickle2s4xi.py
ξ »pickle2t4xi.py
ξ »pickle2v4xi.py
ξ pickling to context
ξ »print4xi.py
ξ dragonized to context

May 8, 2011
ξ tested all (8) processing units: 'APU, ,CPU','DPU', 'GPU', PPU', 'RPU', SPU', 'VPU'

May 5, 2011
ξ »device4xi.py
ξ »device4xi5test.py
ξ tests for all 8 processing units
ξ »apu2device4xi.py
ξ »dpu2device4xi.py
ξ »ppu2device4xi.py
ξ »rpu2device4xi.py
ξ »spu2device4xi.py
ξ »vpu2device4xi.py
ξ 8 processing units
ξ »actor2a4xi.py
ξ »actor2d4xi.py
ξ »actor2g4xi.py
ξ »actor2i4xi.py
ξ »actor2p4xi.py
ξ »actor2r4xi.py
ξ »actor2s4xi.py
ξ »actor2v4xi.py
ξ actors for devices and processing units
ξ »pickle2a4xi.py
ξ »pickle2d4xi.py
ξ »pickle2g4xi.py
ξ »pickle2i4xi.py
ξ »pickle2p4xi.py
ξ »pickle2r4xi.py
ξ »pickle2s4xi.py
ξ »pickle2v4xi.py
ξ pickling to devices and processing units
ξ »print4xi.py
ξ dragonized to devices and processing units

May 4, 2011
ξ device4xi.py, cpu2device4xi.py and gpu2device4xi.py programmed and tested to handle devices CPU and GPU in system !
ξ reported the bug in device IDs to AMD OpenCL forum - AMD to fix this bug in their next release of AMD OpenCL SDK!
ξ decided processing unit:
ξ 'APU' = ACE - 4033
ξ 'CPU' = CPU - 4017
ξ 'DPU' = DIGITAL - 4018
ξ 'GPU' = GPU - 4021
ξ 'PPU' = PHYSICS - 4022
ξ 'RPU' = REASONER - 4024
ξ 'SPU' = SENSOR - 4012
ξ 'VPU' = VIDEO - 4005

ξ »device4xi.py
ξ »device4xi5test.py
ξ tested with both GPU and CPU integrated to device management !
ξ »device4xi5test.txt
ξ »ace-device4xi5test.xml
ξ »reason-device4xi5test.xml
ξ »sense-device4xi5test.xml
ξ »gpu2device4xi.py
ξ »gpu2device4xi5test.py
ξ programmed GPU and changed all device IDs in device4xi.py to have only three characters (CPU,GPU,VPU...)

ξ »actor2i4xi.py
ξ »actor2g4xi.py
ξ »actor2s4xi.py
ξ »pickle2i4xi.py
ξ »pickle2g4xi.py
ξ »pickle2s4xi.py
ξ »print4xi.py
ξ integrated to multiprocessing4xi dragonized trace system device4xi.py, cpu2device4xi.py and gpu2device4xi.py

May 3, 2011
ξ »device4xi.py
ξ »device4xi5test.py
ξ »device4xi5test.txt
ξ »ace-device4xi5test.xml
ξ »reason-device4xi5test.xml
ξ »sense-device4xi5test.xml
ξ tested after integrating cpu4xi.py functions
ξ »cpu2device4xi.py
ξ »cpu2device4xi5test.py
ξ uses OS to get the processor name
ξ added handling of 60 attributes to CPU based on OpenCl specifications

May 2, 2011
ξ »cpu2device4xi.py
ξ programmed to manage CPU resources for OpenCl4Xi - device4xi.py will use this module services
ξ »cpu2device4xi5test.py
ξ »cpu2device4xi5test.txt
ξ »ace-cpu2device4xi5test.xml
ξ »reason-cpu2device4xi5test.xml
ξ »sense-cpu2device4xi5test.xml
ξ more attributes for CPU
ξ »cpu_corecount4xi
ξ used to detect the number of available cores in CPU
ξ »actor2i4xi.py
ξ »actor2g4xi.py
ξ »actor2s4xi.py
ξ »actor2c4xi.py
ξ added functions init2cpu4xi, set2cpu4xi, get2cpu4xi and class CPU4Xi and defined colors
ξ »html-color-codes
ξ used to define colors for actors
ξ »print4xi.py
ξ embedded trace for init2cpu4xi, set2cpu4xi, get2cpu4xi and class CPU4Xi
ξ »pickle2i4xi.py
ξ »pickle2g4xi.py
ξ »pickle2s4xi.py
ξ »pickle2c4xi.py

May 1, 2011
ξ »device4xi.py
ξ »device4xi5test.py
ξ »device4xi5test.txt
ξ »ace-device4xi5test.xml
ξ »reason-device4xi5test.xml
ξ »sense-device4xi5test.xml
ξ tested by setting ID and TYPE for CPU and GPU
ξ »actor2i4xi.py
ξ »actor2g4xi.py
ξ »actor2s4xi.py
ξ »actor2d4xi.py
ξ added functions init2device4xi, set2device4xi, get2device4xi and class Device4Xi and defined colors
ξ »html-color-codes
ξ used to define colors for actors
ξ »print4xi.py
ξ embedded trace for init2device4xi, set2device4xi, get2device4xi and class Device4Xi

April 28, 2011
ξ »device4xi.py
ξ started to program device4xi.py as a base class for all OpenCL devices in the system
ξ »actor2i4xi.py
ξ »actor2g4xi.py
ξ »actor2s4xi.py
ξ »actor2p4xi.py
ξ added functions and class of platforminfo4xi.py and platformids4xi.py as actors

April 27, 2011
ξ »platforminfo4xi5test.py
ξ »platforminfo4xi.py
ξ »platformids4xi5test.py
ξ »platformids4xi.py
ξ added smart return codes to depict both the successed and failed steps taken by the module being traced - improvement to OpenCL!

April 26, 2011
ξ »platforminfo4xi5test.py
ξ »platforminfo4xi.py
ξ programmed and tested OpenCL Platform information API using information provided by OpenCL 1.1 ATI-Stream-v2.3 SDK
ξ »pickle2i4xi.py
ξ »pickle2g4xi.py
ξ »pickle2s4xi.py
ξ »pickle2p4xi.py
ξ added pickling for the functions and the class of platforminfo4xi.py

April 21, 2011
ξ »platformids4xi5test.py
ξ tested
ξ »platformids4xi.py
ξ embedded dragonized trace
ξ »sense-platformids4xi5test.xml
ξ »reason-platformids4xi5test.xml
ξ »ace-platformids4xi5test.xml
ξ XML trace
ξ »print4xi.py
ξ added trace for platformids4xi.py
ξ »pickle2i4xi.py
ξ »pickle2g4xi.py
ξ »pickle2s4xi.py
ξ »pickle2p4xi.py
ξ added pickling for functions and class of platformids4xi.py

April 20, 2011
ξ »platformids4xi.py
ξ programmed test module for platformids4xi.py
ξ »platformids4xi5test.py
ξ programmed test module for platformids4xi.py

April 19, 2011
ξ downloaded OpenCL include files ξ »#005
ξ set and tested environment ξ »#001 ξ »#002 ξ »#003 ξ »#004

April 18, 2011
ξ »z2skeleton4xi5test.py
ξ »z2skeleton4xi.py
ξ »z2skeleton4xi5test.txt
ξ »sense-z2skeleton4xi5test.xml
ξ »reason-z2skeleton4xi5test.xml
ξ »ace-test-z2skeleton4xi5test.xml
ξ skeleton for Scope4Xi modules - with dragonized tagging

ξ »parse2scope4xi.py
ξ »version4xi.py
ξ »parse2scope4xi.txt
============================================================================================================================================
PARSED TOTALLY 36 TAGS IN : 32 MODULES 06:46:21 04/18/11 Pacific Daylight Time
+ OK PARSING ..//..//..//..//..// scope4xi//041721//zap//lib// MODULES 06:46:21 04/18/11 Pacific Daylight Time
+ OK EXPLORING FOLDER ..//..//..//..//..// scope4xi//041721//zap//lib// 06:46:21 04/18/11 Pacific Daylight Time
============================================================================================================================================

ξ »zapimport2ball4xi.py
ξ imports zapped Python module with 3D-shots and creates HTML file
ξ »yoke4xi.py
ξ yoke = to join - in this case input to multiple channels
ξ created batch files at E:\SCOPE4Xi\041721\zap\cc\bat such as all2c.bat
ξ created alphabet subfolders at E:\SCOPE4Xi\041721\zap\lib - each one is one domain
ξ »version4xi.py
ξ each alphabet folder has this module
ξ decided to move scope instead of further debugging boost whihc is not Python 3.3 compatible and is too large & has its own script

~[Σ] ~[Ω] ~[Δ]!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Small & Smart Inc reserves rights to change this document without any notice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~