Suite Summary
suites(s) passed
suites(s) failed,
others
Tests Summary
95 test(s) passed
19 test(s) failed,
0 others
Pass Percentage
-
Cluster Configuration: DRS-Enabled.Vester.ps1Passed
-
Cluster Configuration: DRS-Level.Vester.ps1Passed
-
Cluster Configuration: DRS-Mode.Vester.ps1Failed
-
Cluster Configuration: HA-Enabled.Vester.ps1Passed
-
Host Configuration: Account-Lockout.Vester.ps1Passed
-
Host Configuration: Account-UnlockTime.Vester.ps1Passed
-
Host Configuration: Advanced-Kernel-iovDisableIR.Vester.ps1Passed
-
Host Configuration: BDPU-Filter.Vester.ps1Passed
-
Host Configuration: DCUI-Access.Vester.ps1Passed
-
Host Configuration: DCUI-Timeout.Vester.ps1Passed
-
Host Configuration: Disk-MaxLUN.Vester.ps1Passed
-
Host Configuration: DNS-Address.Vester.ps1Failed
-
Host Configuration: NetDump-Settings.Vester.ps1Passed
-
Host Configuration: NetDump-SettingsEnable.Vester.ps1Passed
-
Host Configuration: NTP-Servers.Vester.ps1Passed
-
Host Configuration: NTP-Service-Policy.Vester.ps1Failed
-
Host Configuration: NTP-Service.Vester.ps1Failed
-
Host Configuration: Password-Policy.Vester.ps1Passed
-
Host Configuration: SSH-InteractiveTimeout.Vester.ps1Passed
-
Host Configuration: SSH-Service-Policy.Vester.ps1Failed
-
Host Configuration: SSH-Service.Vester.ps1Passed
-
Host Configuration: SSH-Timeout.Vester.ps1Passed
-
Host Configuration: SSH-Warning.Vester.ps1Passed
-
Host Configuration: Syslog-Firewall.Vester.ps1Passed
-
Host Configuration: Syslog-Server.Vester.ps1Passed
-
Host Configuration: TPS-ForceSalting.Vester.ps1Passed
-
Host Configuration: VIB-AcceptanceLevel.Vester.ps1Passed
-
VM Configuration: Boot-Delay.Vester.ps1Passed
-
VM Configuration: CDDrive-Host.Vester.ps1Failed
-
VM Configuration: CDDrive-ISO.Vester.ps1Passed
-
VM Configuration: CPU-Limits.Vester.ps1Passed
-
VM Configuration: CPU-Reservation.Vester.ps1Passed
-
VM Configuration: Memory-Limits.Vester.ps1Passed
-
VM Configuration: Memory-Reservation.Vester.ps1Passed
-
VM Configuration: Snapshot-Retention.Vester.ps1Passed
-
VM Configuration: Sync-TimeSettings.Vester.ps1Passed


Kodak KDS TWAIN Driver
Debugging Guide
03-July-2012
Contents
1.0 Overview
2.0 Finding the Driver Files
3.0 Configuring the System
4.0 Dumping the Data Files
5.0 Dumping the Image Files
1.0 Overview
If sending information to Kodak about the TWAIN driver, we recommend including log data, which will result in a quicker diagnosis. This document should be helpful to select what to send. If in doubt, send everything you can.
The TWAIN driver debugs most problems through its logging system. This logging system is reasonably sophisticated, and can be configured to focus on specific areas, as needed. The most common kinds of logging configurations are as follows:
Logging everything: recording all activity. Occasionally this is the best way to capture needed information, especially if the problem is easily reproducible, but not obviously a problem with either the application or the scanner. Logs generated this way tend to be very large, and full of a lot of information. (Debug=1)
Database Dumping: (5.x only) used to take a snapshot of the main database elements in the driver. (Debug=256)
Image Dumping: used to capture images as soon as they are transferred from the scanner, and before they are processed or passed to the application.
2.0 Finding the Driver Files
All Kodak TWAIN driver files are accessible through the following path:
%winbootdir%\twain_32\kodak
Where %winbootdir% is the path to the Windows directory, which is usually either C:\WINDOWS or C:\WINNT. If you are not sure what this is you can do the following to find it out. This works for all versions of Windows.
1) Click on START
2) Select RUN
3) Type in COMMAND and hit the Enter key
4) Type SET in the DOS window
5) Look for WINBOOTDIR
When you look in the %winbootdir%\twain_32\kodak you may see several directories and files. Look for anything beginning with the letters KDS; these contain the Kodak TWAIN drivers. Pick the one that matches your scanner. You can find the version at the top of the readme.txt file.
kds_i30_i40 - Version 6.x i30/i40 driver
kds_i100 - Version 6.x i100 driver
kds_i200 - Version 4.x i200 driver
kds_i600 - Version 5.x or 6.x i600 driver
kds_i800 - Version 4.x or 6.x i800 driver
kds_i1200 - Version 7.x i1200 driver
kds_i1300 - Version 7.x i1300 driver
kds_i1400 - Version 9.x i1400 driver
kds_i1800 - Version 8.x i1800 driver
kds_i1100 - Version 9.x i1100 driver
kds_i700 - Version 9.x i700 driver
kds_i4200_i4600 - Version 10.x i4000 driver
kds_i5000 - Version 11.x i5000 driver
kds_i2000 - Version 11.x i2000 driver
kds_i900 - Version 11.x i900 driver
kds_i2900 - Version 12.x i2900 driver
kds_i3000 - Version 12.x i3000 driver
kds_pss††† - Version 12.x PS50/PS80 driver
3.0 Configuring the System
If you are using a 2/3.x driver, then edit the const.ini file. If you are using a 4/5/6.x driver, then click on the file called a shortcut to const.ini to edit the file.
Inside of this file you will find two values near the top.
Debug=0
DebugFilter=
These are the switches used to configure the Kodak TWAIN driver logging system. By default they are turned off, so that the driver will only record a small amount of information in the event of an error.
The recommended values for Debug are as follows:
Debug=0 - record nothing but errors
Debug=1 - record everything
Debug=7 - record everything and flush to disk
Debug=64 - record just the memory usage
Debug=256 - (5.x only) dump the data files
4.0 Dumping the Data Files
This is available with the version 5/6.x drivers. If there is doubt about the state of the database or the language files or the device configuration data, then it is possible to dump those files at the start of the session. This is done by setting Debug=256 in the const.ini file.
The files all start with the letters KDS and are placed in the userís temp directory. Unfortunately, there is no single, common way to find this directory across all versions of Windows, so rather than try to describe how itís done for each OS, we recommend that you search on your Windows OS disk (usually C:\) for all occurrences of KDS*.TXT, finding the files:
KdsDbFixed.txt
KdsDeviceConfig.txt
KdsLabel.txt
KdsLookupGui.txt
KdsLookupTwain.txt
So, if youíre looking for everything possible to send when looking for help, feel free to include these files.
5.0 Dumping the Image Files
Not all drivers support this, but those that do will show a Dump tab in the TWAIN GUI when it is run from the Scanner Validation Tool (SVT), if the user has the right license level.
You have to contact Kodak to get a license.
For all scanners the tab offers a way to write images to disk before they are passed up to the application.
The first option provides a way to guarantee that the transfer of the image from the driver to the application did not change it in any way.
The second option dumps the data before it is processed by the driver. This Ďrawí image is the one that we would want to see if there are questions about image quality. Itís also the image you need to use if you want to feed it back into the driver using the simulator.


I wish, now, to make an appeal to the hearts and minds of some ten thousand of my brethren and sisters that reside in this land, by asking you the question, if you are willing to bring your tithes and offerings into the storehouse of the Lord, sufficient to purchase the mouthpiece or bell for the temple of the lord? my faith is that your answer will be yes.
iXXwishXXnowXXto wishXXnowXXtoXXmake nowXXtoXXmakeXXan toXXmakeXXanXXappeal makeXXanXXappealXXto anXXappealXXtoXXthe appealXXtoXXtheXXhearts toXXtheXXheartsXXand theXXheartsXXandXXminds heartsXXandXXmindsXXof andXXmindsXXofXXsome mindsXXofXXsomeXXten ofXXsomeXXtenXXthousand someXXtenXXthousandXXof tenXXthousandXXofXXmy thousandXXofXXmyXXbrethren ofXXmyXXbrethrenXXand myXXbrethrenXXandXXsisters brethrenXXandXXsistersXXthat andXXsistersXXthatXXreside sistersXXthatXXresideXXin thatXXresideXXinXXthis resideXXinXXthisXXland inXXthisXXlandXXby thisXXlandXXbyXXasking landXXbyXXaskingXXyou byXXaskingXXyouXXthe askingXXyouXXtheXXquestion youXXtheXXquestionXXif theXXquestionXXifXXyou questionXXifXXyouXXare ifXXyouXXareXXwilling youXXareXXwillingXXto areXXwillingXXtoXXbring willingXXtoXXbringXXyour toXXbringXXyourXXtithes bringXXyourXXtithesXXand yourXXtithesXXandXXofferings tithesXXandXXofferingsXXinto andXXofferingsXXintoXXthe offeringsXXintoXXtheXXstorehouse intoXXtheXXstorehouseXXof theXXstorehouseXXofXXthe storehouseXXofXXtheXXlord ofXXtheXXlordXXsufficient theXXlordXXsufficientXXto lordXXsufficientXXtoXXpurchase sufficientXXtoXXpurchaseXXthe toXXpurchaseXXtheXXmouthpiece purchaseXXtheXXmouthpieceXXor theXXmouthpieceXXorXXbell mouthpieceXXorXXbellXXfor orXXbellXXforXXthe bellXXforXXtheXXtemple forXXtheXXtempleXXof theXXtempleXXofXXthe templeXXofXXtheXXlord ofXXtheXXlordXXmy theXXlordXXmyXXfaith lordXXmyXXfaithXXis myXXfaithXXisXXthat faithXXisXXthatXXyour isXXthatXXyourXXanswer thatXXyourXXanswerXXwill yourXXanswerXXwillXXbe answerXXwillXXbeXXyes
iXXwishXXnow wishXXnowXXto nowXXtoXXmake toXXmakeXXan makeXXanXXappeal anXXappealXXto appealXXtoXXthe toXXtheXXhearts theXXheartsXXand heartsXXandXXminds andXXmindsXXof mindsXXofXXsome ofXXsomeXXten someXXtenXXthousand tenXXthousandXXof thousandXXofXXmy ofXXmyXXbrethren myXXbrethrenXXand brethrenXXandXXsisters andXXsistersXXthat sistersXXthatXXreside thatXXresideXXin resideXXinXXthis inXXthisXXland thisXXlandXXby landXXbyXXasking byXXaskingXXyou askingXXyouXXthe youXXtheXXquestion theXXquestionXXif questionXXifXXyou ifXXyouXXare youXXareXXwilling areXXwillingXXto willingXXtoXXbring toXXbringXXyour bringXXyourXXtithes yourXXtithesXXand tithesXXandXXofferings andXXofferingsXXinto offeringsXXintoXXthe intoXXtheXXstorehouse theXXstorehouseXXof storehouseXXofXXthe ofXXtheXXlord theXXlordXXsufficient lordXXsufficientXXto sufficientXXtoXXpurchase toXXpurchaseXXthe purchaseXXtheXXmouthpiece theXXmouthpieceXXor mouthpieceXXorXXbell orXXbellXXfor bellXXforXXthe forXXtheXXtemple theXXtempleXXof templeXXofXXthe ofXXtheXXlord theXXlordXXmy lordXXmyXXfaith myXXfaithXXis faithXXisXXthat isXXthatXXyour thatXXyourXXanswer yourXXanswerXXwill answerXXwillXXbe willXXbeXXyes
iXXwish wishXXnow nowXXto toXXmake makeXXan anXXappeal appealXXto toXXthe theXXhearts heartsXXand andXXminds mindsXXof ofXXsome someXXten tenXXthousand thousandXXof ofXXmy myXXbrethren brethrenXXand andXXsisters sistersXXthat thatXXreside resideXXin inXXthis thisXXland landXXby byXXasking askingXXyou youXXthe theXXquestion questionXXif ifXXyou youXXare areXXwilling willingXXto toXXbring bringXXyour yourXXtithes tithesXXand andXXofferings offeringsXXinto intoXXthe theXXstorehouse storehouseXXof ofXXthe theXXlord lordXXsufficient sufficientXXto toXXpurchase purchaseXXthe theXXmouthpiece mouthpieceXXor orXXbell bellXXfor forXXthe theXXtemple templeXXof ofXXthe theXXlord lordXXmy myXXfaith faithXXis isXXthat thatXXyour yourXXanswer answerXXwill willXXbe beXXyes
It is justly due to the XXCITY branch of the church to say that, they not only say yes to a bell, but they also say, add a clock to it, and we will not be behind on our part. This is honorable indeed, and I have no doubt, but that, it will meet the feelings of the churches generally, and be pleasing unto them to prove that their tithings and offerings have been laid out to purchase a bell, that when they hear the sound thereof (which may it be the case) they may rejoice that it is the product of their own offerings to the temple of the Lord.
itXXisXXjustlyXXdue isXXjustlyXXdueXXto justlyXXdueXXtoXXthe dueXXtoXXtheXXxxcity toXXtheXXxxcityXXbranch theXXxxcityXXbranchXXof xxcityXXbranchXXofXXthe branchXXofXXtheXXchurch ofXXtheXXchurchXXto theXXchurchXXtoXXsay churchXXtoXXsayXXthat toXXsayXXthatXXthey sayXXthatXXtheyXXnot thatXXtheyXXnotXXonly theyXXnotXXonlyXXsay notXXonlyXXsayXXyes onlyXXsayXXyesXXto sayXXyesXXtoXXa yesXXtoXXaXXbell toXXaXXbellXXbut aXXbellXXbutXXthey bellXXbutXXtheyXXalso butXXtheyXXalsoXXsay theyXXalsoXXsayXXadd alsoXXsayXXaddXXa sayXXaddXXaXXclock addXXaXXclockXXto aXXclockXXtoXXit clockXXtoXXitXXand toXXitXXandXXwe itXXandXXweXXwill andXXweXXwillXXnot weXXwillXXnotXXbe willXXnotXXbeXXbehind notXXbeXXbehindXXon beXXbehindXXonXXour behindXXonXXourXXpart onXXourXXpartXXthis ourXXpartXXthisXXis partXXthisXXisXXhonorable thisXXisXXhonorableXXindeed isXXhonorableXXindeedXXand honorableXXindeedXXandXXi indeedXXandXXiXXhave andXXiXXhaveXXno iXXhaveXXnoXXdoubt haveXXnoXXdoubtXXbut noXXdoubtXXbutXXthat doubtXXbutXXthatXXit butXXthatXXitXXwill thatXXitXXwillXXmeet itXXwillXXmeetXXthe willXXmeetXXtheXXfeelings meetXXtheXXfeelingsXXof theXXfeelingsXXofXXthe feelingsXXofXXtheXXchurches ofXXtheXXchurchesXXgenerally theXXchurchesXXgenerallyXXand churchesXXgenerallyXXandXXbe generallyXXandXXbeXXpleasing andXXbeXXpleasingXXunto beXXpleasingXXuntoXXthem pleasingXXuntoXXthemXXto untoXXthemXXtoXXprove themXXtoXXproveXXthat toXXproveXXthatXXtheir proveXXthatXXtheirXXtithings thatXXtheirXXtithingsXXand theirXXtithingsXXandXXofferings tithingsXXandXXofferingsXXhave andXXofferingsXXhaveXXbeen offeringsXXhaveXXbeenXXlaid haveXXbeenXXlaidXXout beenXXlaidXXoutXXto laidXXoutXXtoXXpurchase outXXtoXXpurchaseXXa toXXpurchaseXXaXXbell purchaseXXaXXbellXXthat aXXbellXXthatXXwhen bellXXthatXXwhenXXthey thatXXwhenXXtheyXXhear whenXXtheyXXhearXXthe theyXXhearXXtheXXsound hearXXtheXXsoundXXthereof theXXsoundXXthereofXXwhich soundXXthereofXXwhichXXmay thereofXXwhichXXmayXXit whichXXmayXXitXXbe mayXXitXXbeXXthe itXXbeXXtheXXcase beXXtheXXcaseXXthey theXXcaseXXtheyXXmay caseXXtheyXXmayXXrejoice theyXXmayXXrejoiceXXthat mayXXrejoiceXXthatXXit rejoiceXXthatXXitXXis thatXXitXXisXXthe itXXisXXtheXXproduct isXXtheXXproductXXof theXXproductXXofXXtheir productXXofXXtheirXXown ofXXtheirXXownXXofferings theirXXownXXofferingsXXto ownXXofferingsXXtoXXthe offeringsXXtoXXtheXXtemple toXXtheXXtempleXXof theXXtempleXXofXXthe templeXXofXXtheXXlord
itXXisXXjustly isXXjustlyXXdue justlyXXdueXXto dueXXtoXXthe toXXtheXXxxcity theXXxxcityXXbranch xxcityXXbranchXXof branchXXofXXthe ofXXtheXXchurch theXXchurchXXto churchXXtoXXsay toXXsayXXthat sayXXthatXXthey thatXXtheyXXnot theyXXnotXXonly notXXonlyXXsay onlyXXsayXXyes sayXXyesXXto yesXXtoXXa toXXaXXbell aXXbellXXbut bellXXbutXXthey butXXtheyXXalso theyXXalsoXXsay alsoXXsayXXadd sayXXaddXXa addXXaXXclock aXXclockXXto clockXXtoXXit toXXitXXand itXXandXXwe andXXweXXwill weXXwillXXnot willXXnotXXbe notXXbeXXbehind beXXbehindXXon behindXXonXXour onXXourXXpart ourXXpartXXthis partXXthisXXis thisXXisXXhonorable isXXhonorableXXindeed honorableXXindeedXXand indeedXXandXXi andXXiXXhave iXXhaveXXno haveXXnoXXdoubt noXXdoubtXXbut doubtXXbutXXthat butXXthatXXit thatXXitXXwill itXXwillXXmeet willXXmeetXXthe meetXXtheXXfeelings theXXfeelingsXXof feelingsXXofXXthe ofXXtheXXchurches theXXchurchesXXgenerally churchesXXgenerallyXXand generallyXXandXXbe andXXbeXXpleasing beXXpleasingXXunto pleasingXXuntoXXthem untoXXthemXXto themXXtoXXprove toXXproveXXthat proveXXthatXXtheir thatXXtheirXXtithings theirXXtithingsXXand tithingsXXandXXofferings andXXofferingsXXhave offeringsXXhaveXXbeen haveXXbeenXXlaid beenXXlaidXXout laidXXoutXXto outXXtoXXpurchase toXXpurchaseXXa purchaseXXaXXbell aXXbellXXthat bellXXthatXXwhen thatXXwhenXXthey whenXXtheyXXhear theyXXhearXXthe hearXXtheXXsound theXXsoundXXthereof soundXXthereofXXwhich thereofXXwhichXXmay whichXXmayXXit mayXXitXXbe itXXbeXXthe beXXtheXXcase theXXcaseXXthey caseXXtheyXXmay theyXXmayXXrejoice mayXXrejoiceXXthat rejoiceXXthatXXit thatXXitXXis itXXisXXthe isXXtheXXproduct theXXproductXXof productXXofXXtheir ofXXtheirXXown theirXXownXXofferings ownXXofferingsXXto offeringsXXtoXXthe toXXtheXXtemple theXXtempleXXof templeXXofXXthe ofXXtheXXlord
itXXis isXXjustly justlyXXdue dueXXto toXXthe theXXxxcity xxcityXXbranch branchXXof ofXXthe theXXchurch churchXXto toXXsay sayXXthat thatXXthey theyXXnot notXXonly onlyXXsay sayXXyes yesXXto toXXa aXXbell bellXXbut butXXthey theyXXalso alsoXXsay sayXXadd addXXa aXXclock clockXXto toXXit itXXand andXXwe weXXwill willXXnot notXXbe beXXbehind behindXXon onXXour ourXXpart partXXthis thisXXis isXXhonorable honorableXXindeed indeedXXand andXXi iXXhave haveXXno noXXdoubt doubtXXbut butXXthat thatXXit itXXwill willXXmeet meetXXthe theXXfeelings feelingsXXof ofXXthe theXXchurches churchesXXgenerally generallyXXand andXXbe beXXpleasing pleasingXXunto untoXXthem themXXto toXXprove proveXXthat thatXXtheir theirXXtithings tithingsXXand andXXofferings offeringsXXhave haveXXbeen beenXXlaid laidXXout outXXto toXXpurchase purchaseXXa aXXbell bellXXthat thatXXwhen whenXXthey theyXXhear hearXXthe theXXsound soundXXthereof thereofXXwhich whichXXmay mayXXit itXXbe beXXthe theXXcase caseXXthey theyXXmay mayXXrejoice rejoiceXXthat thatXXit itXXis isXXthe theXXproduct productXXof ofXXtheir theirXXown ownXXofferings offeringsXXto toXXthe theXXtemple templeXXof ofXXthe theXXlord
All the churches abroad that will assist us in this thing, will please to forward their donations to me, at Stanley Buildings, Bath Street, XXCITY, with their names and amount of tithings, etc, which will be carefully recorded in the Temple Book, and afterwards transferred to the Book of the Law of the Lord in XXCITY.
allXXtheXXchurchesXXabroad theXXchurchesXXabroadXXthat churchesXXabroadXXthatXXwill abroadXXthatXXwillXXassist thatXXwillXXassistXXus willXXassistXXusXXin assistXXusXXinXXthis usXXinXXthisXXthing inXXthisXXthingXXwill thisXXthingXXwillXXplease thingXXwillXXpleaseXXto willXXpleaseXXtoXXforward pleaseXXtoXXforwardXXtheir toXXforwardXXtheirXXdonations forwardXXtheirXXdonationsXXto theirXXdonationsXXtoXXme donationsXXtoXXmeXXat toXXmeXXatXXstanley meXXatXXstanleyXXbuildings atXXstanleyXXbuildingsXXbath stanleyXXbuildingsXXbathXXstreet buildingsXXbathXXstreetXXxxcity bathXXstreetXXxxcityXXwith streetXXxxcityXXwithXXtheir xxcityXXwithXXtheirXXnames withXXtheirXXnamesXXand theirXXnamesXXandXXamount namesXXandXXamountXXof andXXamountXXofXXtithings amountXXofXXtithingsXXetc ofXXtithingsXXetcXXwhich tithingsXXetcXXwhichXXwill etcXXwhichXXwillXXbe whichXXwillXXbeXXcarefully willXXbeXXcarefullyXXrecorded beXXcarefullyXXrecordedXXin carefullyXXrecordedXXinXXthe recordedXXinXXtheXXtemple inXXtheXXtempleXXbook theXXtempleXXbookXXand templeXXbookXXandXXafterwards bookXXandXXafterwardsXXtransferred andXXafterwardsXXtransferredXXto afterwardsXXtransferredXXtoXXthe transferredXXtoXXtheXXbook toXXtheXXbookXXof theXXbookXXofXXthe bookXXofXXtheXXlaw ofXXtheXXlawXXof theXXlawXXofXXthe lawXXofXXtheXXlord ofXXtheXXlordXXin theXXlordXXinXXxxcity
allXXtheXXchurches theXXchurchesXXabroad churchesXXabroadXXthat abroadXXthatXXwill thatXXwillXXassist willXXassistXXus assistXXusXXin usXXinXXthis inXXthisXXthing thisXXthingXXwill thingXXwillXXplease willXXpleaseXXto pleaseXXtoXXforward toXXforwardXXtheir forwardXXtheirXXdonations theirXXdonationsXXto donationsXXtoXXme toXXmeXXat meXXatXXstanley atXXstanleyXXbuildings stanleyXXbuildingsXXbath buildingsXXbathXXstreet bathXXstreetXXxxcity streetXXxxcityXXwith xxcityXXwithXXtheir withXXtheirXXnames theirXXnamesXXand namesXXandXXamount andXXamountXXof amountXXofXXtithings ofXXtithingsXXetc tithingsXXetcXXwhich etcXXwhichXXwill whichXXwillXXbe willXXbeXXcarefully beXXcarefullyXXrecorded carefullyXXrecordedXXin recordedXXinXXthe inXXtheXXtemple theXXtempleXXbook templeXXbookXXand bookXXandXXafterwards andXXafterwardsXXtransferred afterwardsXXtransferredXXto transferredXXtoXXthe toXXtheXXbook theXXbookXXof bookXXofXXthe ofXXtheXXlaw theXXlawXXof lawXXofXXthe ofXXtheXXlord theXXlordXXin lordXXinXXxxcity
allXXthe theXXchurches churchesXXabroad abroadXXthat thatXXwill willXXassist assistXXus usXXin inXXthis thisXXthing thingXXwill willXXplease pleaseXXto toXXforward forwardXXtheir theirXXdonations donationsXXto toXXme meXXat atXXstanley stanleyXXbuildings buildingsXXbath bathXXstreet streetXXxxcity xxcityXXwith withXXtheir theirXXnames namesXXand andXXamount amountXXof ofXXtithings tithingsXXetc etcXXwhich whichXXwill willXXbe beXXcarefully carefullyXXrecorded recordedXXin inXXthe theXXtemple templeXXbook bookXXand andXXafterwards afterwardsXXtransferred transferredXXto toXXthe theXXbook bookXXof ofXXthe theXXlaw lawXXof ofXXthe theXXlord lordXXin inXXxxcity


Traffic Analysis using IBM DSX Desktop - Example Output
Introduction
Pixiedust Installation
Bokeh - Interactive Web Plotting for Python
Import Pixiedust
Import SF Police incidents data to Notebook using PySpark
Display Incidents
Number of Incidents by Week
Display Incidents by Week
Incidents in Mission
Building PixieApp Dashboard
Dashboard


Simple tests for simple-tropo
This is a simple testing build using
SIMPLE-TROPO
message
token
say
to
network
answerOnMedia
channel
from
name
required
timeout
voice


Jude:
You don't have enough Evil Weapons to get the S80 Grade weapon recipe. Bring me
200 Evil Weapons
and I will exchange them for the
S80 Grade weapon recipe
.
Keep at it!


Create a website for your business and pleasure
Mobile friendly, fast and individual
Welcome to our site Proud Whale. We are working hard for making beautiful, safe, and what is more important - peculiar Web Sites, which perfectly much for your business.
First off all we want you to know why you should work with us:
-
Business research
We are believing in that we can give you the best quality only if we can learn everything about your business. You will talk with our analysts to give them all information for better understanding your business and your preference. Mission of your business, tasks of your business, all this questions are highly important.
-
Business research
We are believing in that we can give you the best quality only if we can learn everything about your business. You will talk with our analysts to give them all information for better understanding your business and your preference. Mission of your business, tasks of your business, all this questions are highly important.
-
Business research
We are believing in that we can give you the best quality only if we can learn everything about your business. You will talk with our analysts to give them all information for better understanding your business and your preference. Mission of your business, tasks of your business, all this questions are highly important.
-
Business research
We are believing in that we can give you the best quality only if we can learn everything about your business. You will talk with our analysts to give them all information for better understanding your business and your preference. Mission of your business, tasks of your business, all this questions are highly important.
-
Business research
We are believing in that we can give you the best quality only if we can learn everything about your business. You will talk with our analysts to give them all information for better understanding your business and your preference. Mission of your business, tasks of your business, all this questions are highly important.
-
Business research
We are believing in that we can give you the best quality only if we can learn everything about your business. You will talk with our analysts to give them all information for better understanding your business and your preference. Mission of your business, tasks of your business, all this questions are highly important.
-
Business research
We are believing in that we can give you the best quality only if we can learn everything about your business. You will talk with our analysts to give them all information for better understanding your business and your preference. Mission of your business, tasks of your business, all this questions are highly important.
-
Business research
We are believing in that we can give you the best quality only if we can learn everything about your business. You will talk with our analysts to give them all information for better understanding your business and your preference. Mission of your business, tasks of your business, all this questions are highly important.
our portfolio
-
ecommerc selling watches
view website -
ecommerc selling watches
view website
-
ecommerc selling watches
view website -
ecommerc selling watches
view website
Let me tell you how it works:
Research
It is really important to understand yours business and to know what makes yours business differ from other companies and make everything work well. Our analyst would find everything we need to make your Site look fabulous.
Prototype
The Prototype is the first step of creating, it doesn’t have the design, but but it is the simple way to find out where the pages would be, how they will work and where will be the information.
Design
After the prototyping - the designer will make the design, on this step you will know how your Site will look like. If you will need to change something - we will make it. It called Edits. You will have 2 free circles of Edits, that’s how you can be sure that we will make everything exactly how you want.
Front End Developing
Our Front End Developer would put the Design into your Site. It is already the half of the way. On this step you will see how your Site would look like in the Web and how it would work with the Design.
On this step you also will have 2 circles of Edits for free.
Back End Developing
And now Back End Developer will make Administration panel, payment system, Google Analytics, E-mail delivery, security system, itc.
The Hosting
And finally we will put your Site on Hosting (it’s like virtual house for your Site). And after that everyone would have opportunity visit the Site.
Filling
Everything well done, and here it's last touch - you need to fill your Site with goods and products, write descriptions and so on. For the extra pay - we can do it for you.

This is it, your Site is Done!
our prices
-
Стандартний сайт
We can make Basic Site for your Business. You will have from 1 to 5 unique pages.
For an example: The main Page, About, Contacts, Price, Blog (with the pre-view)
The Blog page is one unique page, but you can create as much pages as you want on it’s pattern.
Show more detailes4000 $
-
Стандартний сайт з EcommerCe
Виготовляємо для вас базовий сайт з 8 сторінок, і ще + Сторінка категорій товарів, сторінка товару(зможете додавати скільки завгодно таких сторінок), Кошик, Сторінка доставки і оплати.
Інтегруємо платіжну систему за вашим бажанням(Наприклад Pay Pal)
Show more detailes6500 $
-
Індивідуальний сайт
We can make different, Individual Sites, if you don’t want Standard Site and want to add something else to your Standard Site or Standard Site with Ecommerce.
We will add everything you want and need, we can add more pages, or functionality for additional payment.
Show more detailesIndividually
All prices are indicated with a discount and we can change them at any time
We are proposing to our clients, to do not use the templates, so we can make all of your ideas come true with different technologies and web-developing.
Standard Sites and Standard Sites with Ecommerce are made in WordPress Base. It is the most common platform in the world for the creating easy Web-Sites.
If you need more powerful We can use other Frameworks, like Django on Python language of programming, or we can use the other fast and powerful Frameworks on PhP.
For more information you can read Q & A, which includes the most common questions from our customers.
Click here for more information.


In this tutorial, you will create a simple GEOS application that draws text and demonstrates the basic components of a GEOS application. You'll learn how to compile and link the application and explore its source code using the Swat debugger.
1 Creating "Tutorial"
1.1 Setting Up Your Working Directory
1.2 Compiling Your Source Code
1.3 Starting the Emulator and Swat
2 Learning GOC
2.1 TUTORIAL.GP: Geode Parameters File
2.2 TUTORIAL.GOC: Source Code
3 Exploring With Swat
4 Source Code
The application that you'll be working on throughout this tutorial is called, appropriately enough, "Tutorial." In this section you'll create two files: TUTORIAL.GP and TUTORIAL.GOC. The .GP (or "geode parameters") file tells the linker how the application is organized; the .GOC file contains the actual source code. All GEOS applications require these two files.
The first step in creating your application is to set up your Working Directory where you will do all your private development. Because your application is called "Tutorial," you need to create a \TUTORIAL\ subdirectory in your Working Directory to hold the source files (see "Developing In Your Working Branch" for more information).
Now that you've created some source code, it's time to compile your application. First, you will need to create a Makefile and then run the "make" or compilation utility.
When you have completed these steps, your directory should contain some new files, including TUTORIALEC.GEO and your newly created GEOS executable or "geode." The "EC" in the name indicates that you've compiled the error-checking version of your application. The GEOS SDK tools have been set up with some optional compilation features to allow for error-checking code which is useful during development.
Once you've successfully compiled your code, it's time to start up the GEOS emulator and attach Swat, the debugger.
Swat version 2.1 (Feb 14 1997 19:05:55). Using the N9000V11 version of GEOS. SDK version: ntsdk30 Looking for "loader"...c:/pcgeos/N9000V11/Installed/Loader/Text/loaderec.sym Sourcing swat.tcl...done GEOS Attached Stopped in LoadGeos, address 0a06h:0007h LoadGeos: CLD ;DF=0 (loader:0) 1 =>
At this point, Swat is telling you that it has successfully established communications with the target emulator, has started the process of loading the GEOS kernel, and is now waiting for you to type in a command. Type
c
and press the <Enter> key to continue loading the GEOS emulator. The following will appear:
Swat version 2.1 (Feb 14 1997 19:05:55). pcgeosGEOS Attached Stopped in LoadGeos, address 0a06h:0007h LoadGeos: CLD ;DF=0 (loader:0) 1 => save screen1.txt Saving to c:/pcgeos/nfiedler/screen1.txt: 1000 lines (loader:0) 2 => c Looking for "geos Eker"...c:/pcgeos/N9000V11/Installed/Library/Kernel/N9000DE MO/geosec.sym Looking for "os2 Eifs"...c:/pcgeos/N9000V11/Installed/Driver/IFS/DOS/OS2/os2 ec.sym Looking for "netware Eifs"...c:/pcgeos/N9000V11/Installed/Driver/IFS/DOS/NetWare /netwareec.sym netware exited. Looking for "respondrElib"...c:/pcgeos/N9000V11/Installed/Library/Respondr/N9000 DEMO/respondrec.sym Looking for "rspwr Edrv"...c:/pcgeos/N9000V11/Installed/Driver/Power/Rspwr/N90 00DEMO/rspwrec.sym Thread 1 created for patient geos Thread 2 created for patient geos Looking for "vidmem Edrv"...c:/pcgeos/N9000V11/Installed/Driver/Video/Dumb/VidM em/vidmemec.sym Looking for "swap Elib"...c:/pcgeos/N9000V11/Installed/Library/Swap/swapec.sy m Looking for "disk Edrv"...c:/pcgeos/N9000V11/Installed/Driver/Swap/Disk/diske c.sym Looking for "xms Edrv"...c:/pcgeos/N9000V11/Installed/Driver/Swap/XMS/xmsec. sym Looking for "gdi Elib"...c:/pcgeos/N9000V11/Installed/Library/GDI/GenPC/WIN3 2/gdiec.sym Looking for "gdiKbd Edrv"...c:/pcgeos/N9000V11/Installed/Driver/Keyboard/GDI/gd iKbdec.sym Looking for "nimbus Edrv"...c:/pcgeos/N9000V11/Installed/Driver/Font/Nimbus/nim busec.sym Looking for "stream Edrv"...c:/pcgeos/N9000V11/Installed/Driver/Stream/streamec .sym Looking for "sound Elib"...c:/pcgeos/N9000V11/Installed/Library/Sound/N9000/so undec.sym Looking for "standarddrvr"...c:/pcgeos/N9000V11/Installed/Driver/Sound/Standard/ N9000DEMO/standard.sym Looking for "ui Elib"...c:/pcgeos/N9000V11/Installed/Library/User/N9000/uie c.sym Thread 0 created for patient ui Looking for "styles Elib"...c:/pcgeos/N9000V11/Installed/Library/Styles/N9000/s tylesec.sym Looking for "color Elib"...c:/pcgeos/N9000V11/Installed/Library/Color/N9000/co lorec.sym Looking for "ruler Elib"...c:/pcgeos/N9000V11/Installed/Library/Ruler/N9000/ru lerec.sym Looking for "text Elib"...c:/pcgeos/N9000V11/Installed/Library/Text/N9000/tex tec.sym Looking for "rtcm Elib"...c:/pcgeos/N9000V11/Installed/Library/RTCM/rtcmec.sy m Looking for "ansic Elib"...c:/pcgeos/N9000V11/Installed/Library/AnsiC/ansicec. sym Looking for "vp Elib"...c:/pcgeos/N9000V11/Installed/Library/Foam/OEM/vp_st b/vpec.sym Looking for "foam Elib"...c:/pcgeos/N9000V11/Installed/Library/Foam/Foam/foam ec.sym Looking for "foamdb Elib"...c:/pcgeos/N9000V11/Installed/Library/Foam/DB/foamdb ec.sym Looking for "contdb Elib"...c:/pcgeos/N9000V11/Installed/Library/Foam/Contdb/co ntdbec.sym WARNING(foamdb::FoamDBVisibleRecordEnumWithRange): DB_ENUM_START_ELEMENT_TOO_LAR GE Looking for "securitylib "...c:/pcgeos/N9000V11/Installed/Library/Foam/Security/ security.sym Looking for "rudy Espu"...c:/pcgeos/N9000V11/Installed/Library/SpecUI/Rudy/ru dyec.sym Looking for "simp4bitEdrv"...c:/pcgeos/N9000V11/Installed/Driver/Video/Dumb/Simp 4Bit/WIN32/simp4bitec.sym WARNING(rudy::OLAppEnsureIndicatorCorrect): RUDY_INDICATOR_NOT_FOUND_IS_GEOS_BOO TING_OR_SHUTTING_DOWN Looking for "spool Elib"...c:/pcgeos/N9000V11/Installed/Library/Spool/N9000/sp oolec.sym Thread 0 created for patient spool Looking for "mailbox Elib"...c:/pcgeos/N9000V11/Installed/Library/Mailbox/N9000/ mailboxec.sym Thread 0 created for patient mailbox Looking for "nonts Edrv"...c:/pcgeos/N9000V11/Installed/Driver/Task/NonTS/nont sec.sym Looking for "contlog Elib"...c:/pcgeos/N9000V11/Installed/Library/Foam/ContLog/c ontlogec.sym Looking for "indicatoEapp"...c:/pcgeos/N9000V11/Installed/Appl/FApps/OEM/indicat o/indicate.sym Thread 0 created for patient indicato Looking for "faxfile Elib"...c:/pcgeos/N9000V11/Installed/Library/Fax/File/N9000 /faxfileec.sym Looking for "viewer Elib"...c:/pcgeos/N9000V11/Installed/Library/Foam/Viewer/vi ewerec.sym Looking for "clrfax Egeo"...c:/pcgeos/N9000V11/Installed/Appl/FApps/ClrFax/clrf axec.sym Thread 0 created for patient clrfax Looking for "math Elib"...c:/pcgeos/N9000V11/Installed/Library/Math/mathec.sy m Looking for "ssset Elib"...c:/pcgeos/N9000V11/Installed/Library/Foam/OEM/ssset /sssetec.sym Looking for "scm Elib"...c:/pcgeos/N9000V11/Installed/Library/Foam/OEM/scm/s cmec.sym Thread 0 created for patient scm Looking for "compose Elib"...c:/pcgeos/N9000V11/Installed/Library/Foam/OEM/compo se/composee.sym Looking for "borlandcElib"...c:/pcgeos/N9000V11/Installed/Library/Math/Compiler/ BorlandC/borlandcec.sym Looking for "phone Eapp"...c:/pcgeos/N9000V11/Installed/Appl/FApps/OEM/phone/p honeec.sym Thread 0 created for patient phone Thread 1 created for patient indicato Thread 1 of indicato exited 0 viewer exited. faxfile exited. clrfax exited. Thread 0 of clrfax exited 0 Looking for "serial Edrv"...c:/pcgeos/N9000V11/Installed/Driver/Stream/Serial/s erialec.sym serial exited. GEOS Halted Stopped in DOSIdleHook, address 2796h:1136h DOSIdleHook+17: MOV AX, 5760 (1680h) (geos:0) 3 =>
Each line that begins "Looking for..." indicates that the system is loading a geode (a GEOS executable) and that Swat is looking for its symbol information. Swat also tells you whenever it creates (or exits) a thread for any geode.
Now that the emulator is running with Swat attached, you need to send your source code to the emulator to run it.
Ctrl-C
in the Swat window. At this point, the Swat prompt should appear.
send tutorial
to copy the application to the emulator.
run tutorial
to run the application.
c
to allow execution to continue on the emulator.
After you've followed these steps, your emulator should look like
the screen pictured below.
|
Figure 1: The "Tutorial" application screen. This is how your application will look after you type in the first pieces of code. Notice that it consists only of a blank viewing window and a "Close" button; later you will add code that displays text in this window. |
As you can see, your application consists of an empty window. In the next chapter, you will add procedural code that draws a text string in this window.
By typing in the contents of the source files (both the .GOC and .GP files), you've probably become a little familiar with GOC syntax. GOC is a proprietary superset of standard ANSI C. It supports C routines and functionality and adds its own set of keywords and special syntax. This section will cover basic GOC syntax, including the usage and meaning of various GOC keywords, by giving a line-by-line explanation of the code you entered.
The .GP file tells the Glue linker about an application's general organization. (You can get complete information about all of the possible fields in a .GP file by reading the GP File Keywords reference.) Let's take a look at the code in TUTORIAL.GP to find out what each line means.
name tutorial.app
The
name
field specifies the "patient" name by which Swat will identify the application. Swat thinks of each geode as a patient, so you'll see phrases in Swat like "patient died".
longname "Tutorial Sample Application"
The
longname
field is the name the system displays for this application. For example, if you press
Ctrl-F12
on the emulator (to list the applications in the "Extras" folder), you will see the
longname
for this application displayed. GEOS supports names up to 32 characters in length.
tokenchars "TUTO" tokenid 8
Each application has its own unique identifier to the system. This identifier is a special GEOS data type called a
GeodeToken
. A
GeodeToken
is a data structure comprised of two fields:
tokenchars
tokenid
GeodeTokens
do not conflict with those of other manufacturers. All sample applications, including this tutorial application, use a
tokenid
of 8; for your "real" applications, you should use your company's assigned Manufacturer ID. (Send email to
<EMAIL_ADDRESS>to receive a Manufacturer ID.)type appl, process, single
The type
line tells Glue whether your geode is an application, a driver or a library.
Tutorial, like most GEOS applications, uses the following keywords:
appl
which tells Glue that this geode is an application;
process
which specifies that the geode should be run in its own thread;
single
which specifies that only one copy of the program may run at a time.Because GEOS is a multi-tasking or multi-threaded operating system, it allows more than one thread of execution to run at a time. This enables programs to run in the background. By specifying that your application has a process, you are requesting that it have its own thread of execution. If you were writing a library, you probably wouldn't want to give it a process, figuring that other geodes would be executing the library's code.
class TutorialProcessClass
The
class
line specifies which class will run the process thread. In this case, the
TutorialProcessClass
will be in charge of the process thread. (You will declare
TutorialProcessClass
in the
TUTORIAL.GOC
file.)
appobj TutorialApp
The
appobj
line specifies the "application object" for this application. The application object is the interface between your geode and the rest of the system. (You will declare this object in your source file as well.)
platform n9000v20
Glue will use the
platform
line to make sure that your application doesn't rely on any geodes that aren't present on the GEOS device.
heapspace 3K
The
heapspace
line specifies the maximum amount of memory the application requires on the global memory heap. Note that the value 3K is a wild guess. Once your application is closer to completion, you can use Swat's
heapspace
command to find out how much heap space the application really needs.
library geos library ui
The
library
lines tell Glue which libraries to load for your application. All GEOS libraries are dynamically linked and loaded.
resource APPRESOURCE ui-object resource INTERFACE ui-object
The
resource
lines specify the blocks of memory that your application uses for objects. Breaking up an application into resources allows it to run more efficiently because the system will only load those resources it needs.
The ui-object
keyword signals that the UI thread should run the specified resource. Specifying a UI thread ensures that your application will
have
a UI thread and thus be dual-threaded: the process will run in one thread and UI objects will run in the UI thread. If you don't want the application to have two threads, use the keyword
object
instead of
ui-object
.
Now let's take a look at the source code in TUTORIAL.GOC . (For more information about GOC syntax, see the GEOS Programming chapter.)
@include <stdapp.goh> @include <foam.goh>
The first lines of code contain the
@include
directive. Note the '@' symbol. This symbol is used to denote GOC keywords and distinguish them from regular C syntax.
@include
behaves the same way as
#include
, except that the inclusion will take place when the GOC preprocessor is processing the source code. Generally, you
@include
.GOH files and
#include
regular .H files.
@class TutorialProcessClass, GenProcessClass; @endc;
The
@class
and
@endc
keywords mark the beginning and end of a new class definition. Here, you're defining
TutorialProcessClass
as a subclass of
GenProcessClass
, which means that
TutorialProcessClass
will inherit all the behavior of its parent,
GenProcessClass
.
@classdecl TutorialProcessClass, neverSaved;
Once you define the class, you need to declare it so that the system will know how to build objects of that class. To declare the class, you use the
@classdecl
keyword and because this is the process object, (a special object with no instance data), you also use the
neverSaved
flag. This flag tells the system that no instance data need be saved when the system shuts down.
@start AppResource;
The
@start
keyword defines a resource or block of memory. In this case, you're defining the APPRESOURCE resource. In the
.
GP file, you may recall that this resource holds objects, and that those objects will be run by the UI thread.
@object FoamSubApplicationClass TutorialApp = {
The first object to be declared in the APPRESOURCE resource is the application object,
TutorialApp
. In the .GP file, you specified
TutorialApp
as the application object in the
appobj
line. The application object is responsible for receiving and handling all sorts of system messages and notifications. This is a nontrivial task so the object will be of a class specifically set up to handle this task:
FoamSubApplicationClass
. (Note, on GEOS systems other than the Nokia 9000i Communicator, you would use a
GenApplicationClass
;
FoamSubApplicationClass
is a specialized subclass of
GenApplicationClass
.)
Because the application object provides important information to the system, it needs to live in its own resource; that way, the system can query the application object by loading only that resource which contains it.
The next set of fields contains the application object's instance data. Instance data are characteristics of an object, as defined by the object's class. (This should make more sense as you read on.)
GI_visMoniker = list{ @TutorialTextMoniker };
The GI_visMoniker
field specifies the object's label or name that appears to the user (not to be confused with
TutorialApp
, the name of the object).
The "visMoniker" part of the field name is short for "visual moniker." In GEOS parlance, a "visual moniker" is a text string or graphic used to identify an object to the user. This field is commonly set to a "list" of monikers; the system uses the moniker list to determine which text or graphic to display for your application.
GI_comp = @TutorialPrimary;
The
GI_comp
field specifies the children of a generic UI object. In this case, the only child of the
TutorialApp
object is the
TutorialPrimary
object (which you declare later). (For a detailed description of how objects keep track of their children, see the GEOS Programming chapter.)
Notice that both instance data field names begin with "GI_." The "GI_" stands for "Gen Instance." Because
GenApplicationClass
is a subclass of
GenClass
, it inherits the
GI_visMoniker
field from its parent. By Geoworks' naming conventions, instance data field names begin with the initials of their associated class followed by an "I" for "instance." Thus, any
GenApplicationClass
instance field names would begin "GAI_."
You may be wondering about the syntax for @TutorialPrimary
.
@TutorialPrimary
is actually a reference to the
TutorialPrimary
object. Object references have their own GEOS-specified type called an
optr
.
gcnList( MANUFACTURER_ID_GEOWORKS, GAGCNLT_WINDOWS ) =@TutorialPrimary; }
This line puts the
TutorialPrimary
object,which is the primary window of your application, on a General Change Notification (GCN) list so that it will receive notification when a system-level change has occurred. (For more information about GCN lists, see the gcnList entry in the GEOS Programming chapter.)
This completes the declaration of the
TutorialApp
object.
@visMoniker TutorialTextMoniker = "My Tutorial";
This line contains the string to which the
TutorialApp
's
GI_visMoniker
field refers. The
@visMoniker
keyword stores the string in a GEOS data structure set up strictly for monikers.
@localize "Program Title";
This
@localize
statement doesn't actually affect the program; it simply acts as a hint for someone translating the program to a foreign language. The ResEdit program displays the information in
@localize
statements when it prompts the translator to translate a moniker or string chunk. In this case, for example, when ResEdit prompts the translator to translate the string, "My Tutorial," it will display the string "Program Title" to assist with the translation.
@end AppResource
This line signals the end of the APPRESOURCE declaration.
@start Interface;
Here begins the next resource definition. This resource is called INTERFACE and will hold the basic UI gadgetry for your application.
@object GenPrimaryClass TutorialPrimary = {
The first object to be declared in this resource is
TutorialPrimary
, your application's primary window and an object of
GenPrimaryClass
.
GI_comp = @TutorialView, @TutorialCloseTrigger; }
The first instance data field is
GI_comp
, which specifies the children of
TutorialPrimary
.
@object GenViewClass TutorialView = {
The next object is a
GenViewClass
object called
TutorialView
; this object provides space on the screen for objects to draw themselves.
GVI_horizAttrs = @default | GVDA_NO_LARGER_THAN_CONTENT; GVI_vertAttrs = @default | GVDA_NO_LARGER_THAN_CONTENT; GVI_content = process; }
The
GVI_content
field specifies the top-level object which will appear in the view's drawing space. The
GVI_horizAttrs
and
GVI_vertAttrs
fields specify how the view should size itself in relation to the
content
object's size. Setting the flag GVDA_NO_LARGER_THAN_CONTENT
ensures that the view will be the same size as its content object.
Notice that the
GVI_...Attrs
fields also use the
@default
keyword.
@default
tells the system to expand to the default values for this field (as defined by
GenViewClass
); additional flags are ORed in with the single pipe ("|").
@object GenTriggerClass TutorialCloseTrigger = { GI_visMoniker = "Close";
The last object declared in the INTERFACE resource is
TutorialCloseTrigger
, an object of
GenTriggerClass
.
TutorialCloseTrigger
provides the "Close" button for your application.
GTI_destination = @TutorialApp; GTI_actionMsg = MSG_FSA_RETURN_TO_LAUNCHER;
The GTI_destination
and GTI_actionMsg
fields are GenTrigger instance data fields. GTI_actionMsg
specifies the message that gets sent when the user presses the "Close" button; GTI_destination
specifies the object who will handle the message. (We will discuss messages in more detail in the next chapter; suffice it to say that a message is a signal which may be handled by a set of procedural code defined for a class.)
HINT_SEEK_MENU_BAR; HINT_SEEK_REPLY_BAR; HINT_SEEK_SLOT = 3; }
These hints ensure that the button is placed on the right side of the screen so that it aligns with the buttons on the Nokia 9000i Communicator.
@end Interface;
This line signals the end of the INTERFACE resource definition.
Now that you've successfully compiled your application, you can use Swat to "debug" it. In the Swat window, press
Ctrl-C
to halt the emulator and gain control back in the Swat window. Something similar to the following should appear in your Swat window:
GEOS Halted Stopped in DOSIdleHook, address 277eh:1136h DosIdleHook+17 MOVE AX, 5760 (1680h) (geos:0) 5 =>
"GEOS Halted" indicates that Swat has frozen the emulator. The next two lines of Swat output indicate the address of the current internal routine that is executing. If Swat stopped in a public routine, the address would have been given in relation to the routine name and would have been more readable.
The last line indicates the thread that was executing (on the emulator) when you hit
Ctrl-C
. In this example, the zeroth thread associated with the GEOS geode (the kernel) was executing. To examine the thread associated with your application, type "tutorial." (Recall that this is the value you set in the
name
field of your
TUTORIAL.GP
file [without the suffix].) This tells Swat which thread to switch to.
(geos:0) 5 => tutorial [tutorial:0] 6 =>
The prompt indicates that you are now in the process thread of the
tutorial
geode. If you were in the UI thread, your prompt would read "[tutorial:1]." To change threads within a geode, simply type
:0
or
:1
.
Now try the
where
command to find out what this thread was doing when you stopped the system.
[tutorial:0] 6 => where * 1: near BlockOnLongQueue(), 153dh:c22ah 2: far QueueGetMessage(), 153dh:133ch ------------------------------------------------------------------------------ The event queue for "tutorial:0" is empty ============================================================================== [tutorial:0] 7 =>
These lines tells you that the tutorial thread is idling; it's waiting for a message or something to happen.
Next, use the
gentree
command to examine your application's generic UI object tree.
[tutorial:0] 7 => gentree *TutorialPrimary *TutorialPrimary::GenPrimary (@1, ^l5230h:001eh) "My Tutorial" *TutorialView::GenViewClass (@2, ^l5230h:0020h) ^143b0h:002ah(GenValueClass) (@3, ^15230h:002ah) *TutorialCloseTrigger(GenTriggerClass) (@4, ^15230h:0024h) "Close"
[tutorial:0] 8=>
The
gentree
command prints out a list of all the objects in the tree, along with their class, object references, and monikers. For an example, let's look at the information for the
TutorialView
object:
You can refer to an object by a shortcut that Swat provides, namely, the<EMAIL_ADDRESS>To look at an object's instance data, use the Swat command
pobj
followed by the "@number" designation for the particular object. Try the
pobj
command with the
TutorialView
object.
[tutorial:0] 8 => pobj @2 *TutorialView{GenViewClass} (@5, ^l5230h:0020h) master part: Gen_offset(131) -- ui::GenViewInstance @6: {ui::GenViewInstance (^h21040:502)+131} = { GenInstance GenView_metaInstance = { MetaBase Gen_metaInstance = { ClassStruct _far *MB_class = 3916h:1816h (rudy::CommonUIClassStructu res::OLPaneClass) } LinkPart GI_link = { void _optr LP_next = *TutorialCloseTrigger{GenTriggerClass} (@7, ^l5 230h:0024h) } CompPart GI_comp = { void _optr CP_firstChild = ^l5230h:002ah{GenValueClass} (@8, ^l5230h :002ah) } void _lptr GI_visMoniker = null KeyboardShortcut GI_kbdAccelerator = { KS_PHYSICAL = 0h KS_ALT = 0h KS_CTRL = 0h KS_SHIFT = 0h KS_CHAR_SET = 0h KS_CHAR = C_NULL } GenAttrs GI_attrs = {GA_TARGETABLE} GenStates GI_states = {GS_USABLE, GS_ENABLED} } PointDWFixed GVI_origin = { DWFixed PDF_x = {0.000000} DWFixed PDF_y = {0.000000} } RectDWord GVI_docBounds = { long RD_left = 0 long RD_top = 0 long RD_right = 0 long RD_bottom = 0 } PointDWord GVI_increment = { long PD_x = +20 long PD_y = +15 } PointWWFixed GVI_scaleFactor = { WWFixed PF_x = {1.000000} WWFixed PF_y = {1.000000} } ColorQuad GVI_color = { byte CQ_redOrIndex = fh ColorFlag CQ_info = CF_INDEX byte CQ_green = 0h byte CQ_blue = 0h } GenViewAttrs GVI_attrs = {GVA_NO_WIN_FRAME, GVA_FOCUSABLE} GenViewDimensionAttrs GVI_horizAttrs = {GVDA_DONT_DISPLAY_SCROLLBAR, GVDA_NO_LARGER_THAN_CONTENT} GenViewDimensionAttrs GVI_vertAttrs = {GVDA_NO_LARGER_THAN_CONTENT} GenViewInkType GVI_inkType = GVIT_PRESSES_ARE_NOT_INK void _optr GVI_content = tuto1:0{TutorialProcessClass}(0000h) (@9, ^l56c0h:0 000h) void _optr GVI_horizLink = null void _optr GVI_vertLink = null } Variable Data: *** No Variable Data *** [tutorial:0] 9 =>
We certainly got a lot of data from that command!
*TutorialView{GenViewClass} (@5, ^l5230h:0020h)
The first line gives the object's class, shortcut and pointer information, similar to the output from gentree
.
The rest of the output consists of the object's instance data. For example:
GenViewDimensionAttrs GVI_horizAttrs = { GVDA_DONT_DISPLAY_SCROLLBAR, GVDA_NO_LARGER_THAN_CONTENT}
These lines show which flags (of type GenViewDimensionAttrs
)
are set for the object's
GVI_horizAttrs
instance data field. Notice that Swat displays both the flag set in your source code, GVDA_NO_LARGER_THAN_CONTENT
, as well as the default flag set by the system, GVDA_DONT_DISPLAY_SCROLLBAR
.
You may recognize some of the instance data fields from your source code. Other fields you may not recognize because you didn't specify values for these fields, allowing the system to use default values instead.
With
pobj
, you took advantage of another Swat feature: command completion.
There is no "pobj
"
Swat command; the command's name is really
"pobject
." Because
"pobject
" was the only
Swat command that begins with p-o-b-j, Swat realized what you meant when you used
"pobj
."
Next let's try a series of exploratory Swat commands:
[tutorial:0] 9 => classes TutorialProcessClass (@10, 42b8h:0040h), off ui::UserClassStructures::GenProcessClass [tutorial:0] 10 =>
The
classes
command lists all classes created by the application. To view the class hierarchy for a particular class, use the
cup
("class up") command.
[tutorial:0] 10 => cup @10 dgroup::TutorialProcessClass (@11, 42b8h:0040h) ui::UserClassStructures::GenProcessClass (@12, 30c4h:11e6h) geos::kcode::ProcessClass (@13, 153dh:a9d5h) geos::kcode::MetaClass (@14, 153dh:a8edh) [tutorial:0] 11 =>
As shown above, you can use the shortcut reference (the "@number") with the
cup
command or you can use the class name or reference address,
e.g.,
cup TutorialProcessClass
or
cup 42b8h:0040h
.
Some other Swat commands you might want to try out:
help
command provides documentation on Swat commands. Try
help stop
.
apropos
command allows you to search the Swat documentation by keyword. Try
apropos instance
.
heapspace
command tells you the amount of memory your application requires; you may recall that this value goes in your
.
GP file on the
heapspace
line. Because this value should reflect a worse-case scenario, it's important to run this command several times towards the end of development so that the figure is accurate.
handles
command scans the entire memory heap and returns information about all handles used by the application.In the next chapter, you'll begin by editing the source code, so prepare to switch over to your editor window.


Part I
Arnold Schwarzenegger has a long one. Michael J. Fox has a short one. Madonna does not use hers. Bill Clinton always uses his. The Pope never uses his. What is it?


$filterProvider
ng
Filters are just functions which transform input to an output. However filters need to be Dependency Injected. To achieve this a filter definition consists of a factory function which is annotated with dependencies and is responsible for creating a filter function.
// Filter registration function MyModule($provide, $filterProvider) { // create a service to demonstrate injection (not always needed) $provide.value('greet', function(name){ return 'Hello ' + name + '!'; }); // register a filter factory which uses the // greet service to demonstrate DI. $filterProvider.register('greet', function(greet){ // return the filter function which uses the greet service // to generate salutation return function(text) { // filters need to be forgiving so check input validity return text && greet(text) || text; }; }); }
The filter function is registered with the $injector
under the filter name suffix with
Filter
.
it('should be the same instance', inject( function($filterProvider) { $filterProvider.register('reverse', function(){ return ...; }); }, function($filter, reverseFilter) { expect($filter('reverse')).toBe(reverseFilter); });
For more information about how angular filters work, and how to create your own filters, see Filters in the Angular Developer Guide.


{% extends "reports/reports_base.html" %} {% load humanize %} {% block extra_link_types %} {% endblock %} {% block subcontent %}
Below is a list of NDNP Awardees that have content in the {{ site_title }} Web Application. Clicking on the name will bring you to a detailed page for the awardee, and clicking on the organization code will perform a search of the MARC Organization database.
| Name | MARC Organization Code | Total Pages | Total Essays |
|---|---|---|---|
| {{ awardee.name }} | {{ awardee.org_code }} | {{ awardee.page_count|intcomma }} | {{ awardee.essays.count|intcomma }} |


Last updated: September 23, 2016
- 1GENERAL CONDITION OF USE
- 1.1 Scope and Definitions
These General Conditions of Use apply to all services provided by Go College (defined herein below). Go College owns and operates the Application (defined herein below) in India.
Defined Terms
“Car Sharing” means the sharing of a Vehicle for a Trip by a Car Owner carrying a Co-Traveller for that Trip in exchange for a Cost Contribution.
“Conditions” mean these General Conditions of Use, including the Good Conduct Charter and Privacy Policy of Go COllege as notified on the Application.
“Cost Contribution” means the amount agreed between the Car Owner and the Co-Traveler in relation to the Trip which is payable by the Co-Traveler as their contribution towards the costs of the Trip.
“Co-Traveller” or “Passenger” means a Member who has accepted an offer to be transported by a Car Owner and includes all other persons who accompany such Member in the Vehicle for the Trip.
“Car Owner” or “Driver” means a Member who through the Application offers to share a car journey with a Co-Traveller in exchange for the Cost Contribution.
“Member” refers to a registered user of the Application.
“Service” refers to any service provided by Go College through the Application to any Member.
“Trip” means a given journey in relation to which a Car Owner and a Co-Traveler have agreed upon a transaction through the Application.
“User Account” means an account with the Application opened by a Member and used in order to access the Service provided by Go College through the Application.
“Vehicle” means the vehicle offered by a Car Owner for Car Sharing.
1.2 Acceptance of Conditions
The Conditions apply to any and all use of the Application by a Member. By using the Application, the Members signify their acceptance to these Conditions in full and agree to be bound by them.
No access to the Services will be permitted unless the Conditions are accepted in full. No Member is entitled to accept part only of the Conditions. If a Member does not agree to the Conditions, such Member may not use the Services.
All Members agree to comply with the Conditions and accept that their personal data may be processed in accordance with the Privacy Policy.
In the event that any Member fails to comply with any of the Conditions, Go College reserves the right, but not the obligation at its own discretion, to withdraw the User Account in question and suspend or withdraw all Services to that Member without notice.
These Conditions are intended to create binding rights and obligations between Members and Go College.
1.2 Variation of the Conditions, Application and Service
Go College reserves the right to modify the Conditions at any time. In addition, Go College may vary or amend the Services provided through the Application, the Application functionality and/ or the “look and feel” of the Application at any time without notice and without liability to Members.
Any modification to the Application, Services or Conditions will take effect as soon as such changes are published on the Application, subject to communication of any material change to the Conditions to the Members in an e-mail.
Members will be deemed to have accepted any varied Conditions in the event that they use any Services offered through the Application following publication of the varied Conditions. Changes will not apply to any bookings which have been made prior to publication of the varied Conditions.
- 2USE OF THE SERVICE
- 2.1 User Account and Accuracy of Information
In order to use the Services each Member must create a User Account and agrees to provide any personal information requested by Go College. In particular, Members will be required to provide their first name, last name, valid telephone number and email address.
Members agree and accept that all of the information they provide to Go College when setting up their User Account and at any other time shall be true, correct, complete and accurate in all respects. Members also agree that any information supplied to Go College or posted on the Application in connection with any Trip, Vehicle or Car Sharing will be true, accurate and complete.
Members agree and understand that Go College does not undertake any verification to confirm the accuracy of any information provided by the Members on the Application or to a Car Owner or Co-Traveler, as the case maybe. Go College will not be liable to any Member in the event that any information provided by another Member is false, incomplete, inaccurate, misleading or fraudulent.
Unless expressly agreed by Go College, Members are limited to one User Account per Member. No User Account may be created on behalf of or in order to impersonate another person.
2.2 No Commercial Activity and Status of Go College
The Application and the Services are strictly limited to providing a Service for Car Owners and Co-Travelers to car share in a private capacity. The Services may not be used to offer or accept car sharing for hire or reward or for profit or in any commercial or professional context. The Services may be used only to offer or accept car sharing in exchange for sharing the cost of the Trip between the Car Owner and the Co-Traveler.
Car Owners agree not to obtain any hire or reward or make profit in any form, from any Trip. The Service and the Cost Contribution may only be used to discharge the Car Owner’s costs and may not be used to generate any hiring charges or reward or profit in any form for the Car Owner. The Car Owner is not entitled to make profit by virtue of the amount of the Cost Contribution, the types of Trips offered by a Car Owner, the frequency of such Trips or the number of Co-Travelers transported. This applies to all activities, arrangements and Services booked using the Application and any additional services or activities which may be agreed between Car Owner and Co-Traveler through the Application.
The Car Owner must not provide any additional services to the Co-Traveler in exchange for hiring charges or any reward or for profit or otherwise (and the Co-Traveler may not accept or ask for any such services) including (without limitation) package delivery, waiting time, additional drop offs and pick-ups and collecting additional passengers (other than the Co-Traveler).
All Trips, collection points and destinations must be pre-agreed through the Application between the Car Owner and Co-Traveler. Car Owners may not collect any Co-Travelers from any location which has not been pre-agreed with the Co-Traveler through the Application.
Members are reminded that using the Services and offering Trips for hire or reward or in a commercial or professional capacity may invalidate a Car Owner’s insurance and invite adverse legal actions by the road transport authorities. Go College shall not be in for any loss or damage incurred by a Member as a result of any or breach by a Member of these Conditions including where any Car Owner (in breach of these terms) offers Services through the Application in a professional or commercial capacity (thereby potentially invalidating their insurance) and breach of any agreement between the Car Owner and the Co-Traveler. Any offering of Trips in violation of the Conditions shall be at the sole risk such Member and Go College shall have no liability towards Members for such violations.
Status of Go College
Neither Go College nor the Application provides any transport services. The Application is a communications platform for Members to transact with one another. Go College does not interfere with Trips, destinations or timings. The agreement for car sharing is between the Car Owner and the Co-Traveler. Go College is not a party to any agreement or transaction between Members, nor is Go College liable in respect of any matter arising which relates to a booking between Members. Go College is not and will not act as an agent for any Member.
Any breach of these Conditions will give rise to immediate suspension of such Member’s User Account and they may be restricted from accessing any further Services.
2.3 Types of Booking and Payment
Go College offers to its Members an online booking service with a view to facilitate the booking of seats by Passengers.
Go College reserves the right not to offer the Booking Service to a Trip o due to: (i) changes to applicable law, changes in the practice of regulatory authorities or changes in case law, (ii) changes to market practices or technology changes, (iii) changes of business considerations underlying the Booking Services, and (iv) other important and valid reasons.
Go College reserves the right to limit the number and/or class of Members eligible to the Booking Service for any Trip.
2. How to book a Car-Sharing for a Trip: The Car Owner provides details of his or her Trip on the Application, specifying date and time for departure and destination points, the amount of the Cost Contribution per seat and all other relevant travel conditions.
The Passenger books one or more seats in the car for that Trip from the Application.
Members accept that given the nature of the service Car Owners and Co-Travelers will have no recourse to Go College for any aspect of the transaction including in relation to cancellation, last minute changes, failure by the Car Owner or the Co-Traveler to turn up or non-payment of the Cost Contribution. In particular it is the Car Owner’s responsibility to collect payment from the Co-Traveler at the time of the Trip.
Go College will not contact either party and will take no other steps whatsoever than those described above to manage the booking. The operation of the Trip is solely managed by the respective Car Owner and Co-Traveler(s).
Please note that Go College reserves the right to change any aspect of the Application or the Service which may include adding new services (which may require payment) or withdrawing any existing Services. Go College does not guarantee that the Application will be functional at all times and Services may be suspended during such period when the Application is not in operation. Go College will not be liable to any of the Members in case where the Application is non-operational.
2.4 Car Owner and Co-Traveler Obligations
Car Owner’s obligations
The Car Owner agrees:
That the Trip shall not be for any fraudulent, unlawful or criminal activity.
That they will procure for the Vehicle, a comprehensive insurance policy, which provides insurance cover to the occupants in the Vehicle and covers third party liability.
That they will present themselves on time and at the place agreed with the specified Vehicle;
That they will immediately inform all Co-Travelers of any change whatsoever to the Trip. If one or more Co-Travelers have made a booking and the Car Owner decides to change any aspect of the Trip, the Car Owner undertakes to contact all Co-Travelers who have made a booking in relation to that Trip and to obtain the agreement of all Co-Travelers to the change. If a Co-Traveler refuses the change, they are entitled to a full refund and without any compensation being paid to the Car Owner.
The Car Owner must comply with the Good Conduct Charter at all times.
The Car Owner must wait for the Co-Traveler at the pickup point for at least 30 minutes after the agreed time (however, the Co-Traveler is expected to be punctual).
Co-Traveler obligations
The Co-Traveler agrees:
That the Trip shall not be for any fraudulent, unlawful or criminal activity.
That they will present themselves on time and at the place agreed with the Car Owner;
That they will immediately inform the Car Owner or Go College if they are required to cancel a Trip.
That they will comply with the Good Conduct Charter at all times.
The Co-Traveler agrees to wait at the pickup point for at least 30 minutes after the agreed time for the Car Owner to arrive.
That they will pay the Cost Contribution to the Car Owner.
If the Co-Traveler or Car Owner fail to comply with any of these terms or any other Conditions Go College reserves the right to keep information relating to the breach, to publish or disclose this information on the Member’s online profile and to suspend or withdraw the Member’s access to the Application.
That they shall ensure that all other persons who accompany the Co-Traveller in the Trip comply with these Conditions as applicable to a Co-Traveller.
2.5 Insurance
The Car Owner agrees and undertakes to take out and maintain a comprehensive insurance to cover third party liability, the occupants of the Vehicle and the Trip offered or booked through the Application. The Car Owner agrees that they will, on request, provide the Co-Traveler with evidence, in advance of the Trip, of the complete validity of its insurance policy. The Car Owner also undertakes to hold a valid driving licence and that the Car Owner will own or will be entitled to use the Vehicle and that the Vehicle will have a valid PUC (Pollution Under Control) certificate and the Co-Traveler is entitled to request evidence of the Car Owner’s insurance, registration certificate (‘log book’), driving licence and PUC certificate at any time up to completion of the Trip.
It is Go College’s understanding that governmental authorities take the view that a Co-Traveler who contributes only towards travel expenses is treated as travelling without hire or reward to the driver, and is therefore a third party passenger who is covered by comprehensive third party insurance policy in India. However Go College gives no warranty or assurance in this regard and it is the Car Owner’s responsibility to verify that their insurance provides adequate cover.
It is up to each Car Owner and Co-Traveler to confirm with each other that the Car Owner is covered by valid insurance. The Car Owner must confirm that their insurance policy allows them to carry Co-Travelers and that their insurance policy covers all Co-Travelers and any accident or incident which may occur during a Trip.
The Car Owner and the Co-Traveler are aware that standard non-commercial insurance policies may refuse to cover loss or damage arising in the event that the Car Owner had made or was seeking to make a profit.
The Car Owner may collect no payment from the Co-Traveler other than the Cost Contribution and the Car Owner must not in any event provide Vehicle on hire or for reward in any form.
The Car Owner therefore undertakes to calculate their expenses (fuel, toll, maintenance, repairs, depreciation and insurance of their vehicle) and guarantees that the total Cost Contributions requested from their Co-Travelers does not result in the Vehicle running for hire or for reward.
If the Car Owner does receive any hiring charges or reward, or if the insurers repudiate or refuse to accept any claim arising during a Trip for any other reason, the Car Owner will be responsible for the financial consequences, losses and damages arising and Go College will not be liable under any circumstances to the Car Owner or the Co-Traveler.
Go College reserves the right, but not the obligation at its own discretion, to suspend immediately the account of a user including the money displayed and to make aware to competent authorities any professional activity.
2.6 Management of Disputes Between Members
Go College may at its sole discretion provide its Members with an online service for resolving disputes. This service is non-binding. Go College is under no obligation to seek to resolve disputes and this service is offered at Go College’s sole discretion and may be withdrawn at any time.
2.7 Verification of IDs and Phone number
By accepting the terms and conditions contained herein, every Member or any person who wishes to register as a Member hereby agrees and consents to the fact that Go College may collect IDs / documents belonging to them including but not limited to passport, PAN card and Aadhaar card for the purpose of verification of the information contained in such IDs / documents by third party service providers.
2.8 Contacting Members
By accepting the terms and conditions contained herein, every Member hereby agrees and gives consent to Go College to communicate via phone calls, sms, email and such other means as Go College may deem fit. Such communications to Members may be recorded through technical support provided by third parties for the purpose of training, quality and for regularly updating the Members about the services of Go College.
- 3DISCLAIMER OF LIABILITY
- 3.1 Members may access the Services on the Application at their own risk and using their best and prudent judgment before entering into any arrangements with other Members through the Application. Go College will neither be liable nor responsible for any actions or inactions of Members nor any breach of conditions, representations or warranties by the Members. Go College hereby expressly disclaims and any and all responsibility and liability in arising out of the use of the Application.
3.2 Go College expressly disclaims any warranties or representations (express or implied) in respect of Trips, accuracy, reliability and completeness of information provided by Members, or the content (including details of the Trip and Cost Contribution) on the Application. While Go College will take precautions to avoid inaccuracies in content of the Application, all content and information, are provided on an as is where is basis, without warranty of any kind. Go College does not implicitly or explicitly support or endorse any of the Members availing Services from the Application.
3.3 Go College is not a party to any agreement between a Car Owner and Co-Traveler and will not be liable to either the Car Owner or the Co-Traveler unless the loss or damage incurred arises due to Go College’s negligence.
3.4 Go College shall not be liable for any loss or damage arising as a result of:
A false, misleading, inaccurate or incomplete information being provided by a Member;
The cancellation of a Trip by a Car Owner or Co-Traveler;
Any failure to make payment of a Cost Contribution (for the free service without booking);
Any fraud, fraudulent misrepresentation or breach of duty or breach of any of these Conditions by a Car Owner or Co-Traveler before, during or after a Trip.
Go College will not be liable to any Member for any business, financial or economic loss or for any consequential or indirect loss such as lost reputation, lost bargain, lost profit, lost of anticipated savings or lost opportunity arising as a result of the services provided by Go College (whether suffered or incurred as a result of the Go College’s negligence or otherwise) except in the case of fraud, wilful concealment or theft.
Go College will not be liable to any Member in relation to any Trip unless Go College is notified of a claim relating to that Trip within 3 months of completion of the Trip
Given that Car Owners are required to hold valid insurance to cover a Trip and given that Go College’s service is limited to putting Car Owners and Co-Travelers in touch with each other and cannot oversee any Trip, Members accept that the limitations on the Go College’s liability set out above are reasonable.
- 4INDEMNITY AND RELEASE
-
4.1 Members will indemnify and hold harmless Go College, its subsidiaries, affiliates and their respective officers, directors, agents and employees, from any claim or demand, or actions including reasonable attorney’s fees, made by any third party or penalty imposed due to or arising out of your breach of these Conditions or any document incorporated by reference, or your violation of any law, rules, regulations or the rights of a third party.
4.2 Members release Go College and/or its affiliates and/or any of its officers and representatives from any cost, damage, liability or other consequence of any of the actions/inactions of the Members and specifically waiver any claims or demands that they may have in this behalf under any statute, contract or otherwise.
- 5GENERAL TERMS
- 5.1 Relationship
No arrangement between the Members and Go College shall constitute or be deemed to constitute an agency, partnership, joint venture or the like between the Members and Go College.
5.2 Suspension or Withdrawal of Application Access
In the event of non-compliance on your part with all or some of the Conditions, you acknowledge and accept that Go College can at any time, without prior notification, interrupt or suspend, temporarily or permanently, all or part of the service or your access to the Application (including in particular your User Account)..
5.3 Intellectual Property
The format and content included on the Application, such as text, graphics, logos, button icons, images, audio clips, digital downloads, data compilations, and software, is the property of Go College, its affiliates or its content suppliers and is protected by India and international copyright, authors’ rights and database right laws.
All rights are reserved in relation to any registered and unregistered trademarks (whether owned or licensed to Go College) which appear on the Application.
The Application or any portion of the Application may not be reproduced, duplicated, copied, sold, resold, viApplicationd, or otherwise exploited for any commercial purpose without the express written consent of Go College. No person is entitled to systematically extract and/or re-utilise parts of the contents of the Application without the express written consent of Go College. In particular, the use of data mining, robots, or similar data gathering and extraction tools to extract (whether once or many times) for re-utilisation of any substantial parts of this Application is strictly prohibited.
5.4 Content of the Application Provided by the Members
By displaying content on this Application, Members expressly grant a license to Go College to display the content and to use it for any of our other business purposes.
Members of this Application are expressly asked not to publish any defamatory, misleading or offensive content or any content which infringes any other persons intellectual property rights (e.g. copyright). Any such content which is contrary to Go College’s policy and Go College does not accept liability in respect of such content, and the Member responsible will be personally liable for any damages or other liability arising and agrees to indemnify Go College in relation to any liability it may suffer as a result of any such content. However as soon as Go College becomes aware of infringing content, Go College shall do everything it can to remove such content from the Application as soon as possible.


#{text['display.title']}
#{text['display.heading']}
Below is a list of attributes that were gathered in FileUpload.java.
Friendly Name:
${friendlyName}
Filename:
${fileName}
File content type:
${contentType}
File size:
${size}
File Location:
The file has been written to:
${location}
#{text['button.done']}
Upload Another


This is unique place to go. There are a lot of things to do, and the millions hikes with a majestic view.
“There is nothing so American as our national parks…. The fundamental idea behind the parks…is that the country belongs to the people, that it is in process of making for the enrichment of the lives of all of us.”
Calling all adventurers! Angels Landing is one of the world's most renowned hiking destinations — though it's certainly not for the faint of heart. With dizzying heights, and hairpin turns, the thousands of hikers it draws every year might not know exactly what they're getting themselves into.


This sample showcases basic Voice Synthesis functionality in Windows, using WinRT APIs to convert text to speech


means crossbar landing fastener gear movable associated second airframe portion stationary wheel relative blocking skid transverse connection centering device slide structure position sloping ground longitudinal comprise return axle aircraft includes bearing central given skids CLAIM-TEXT:. claim elevation fastened pilot said secured suitable Furthermore, according claim-ref[claim order resilient co-operating crossbar, crossbars figref[FIG. ground. provided center direction arranged lateral movement predetermined airframe, collective curvature example, flight lever pitch assembly block connect having acting connecting ground, helicopter including plate reference terrain, airframe. allowing arc circumstances, connected crossbar. i.e. independent invention radius reaction rotor wheel. figref[FIGS. force include means, moving observed passing resting skid, touches abutment blades catches comprises comprising document-id:: horizontal landing, position. shapes sliding spring understood uphill Thus, [addressbook]: action-date: carrier causes cyclic devices generating-office:: interfering landing. particular possible presents shown slot stage substantially Classification: No. applicant capable citation: cited concave downhill extending following gear, limit longer parallel plates possesses present presenting reducing referred returning slope symmetry tending terrain. wheels Pat. U.S. [patcit]: addition, aircraft, anteroposterior arrow catches. contact contrast, crossbars. does e.g. end equivalent facing fastening flight, insofar located means. plane portion, pressing rear resonance rotorcraft serves shape structure, teeth wheel,


{% import '_includes/forms' as forms %}
Enabling this will allow any emails EXCEPT those in the list.


{%extends 'base.html'%} {% load static %} {% load bootstrap5 %} {% block content %}
Did not find a user with that username


Recent Updates (Sept. 26, 2020)
- Runestone 5.2 - is live - with some important updates
- Question Numbering The way that we display question numbers has changed. It is now consistent between the page and the assignment builder! This is cosmetic only and does not affect assignments or grades.
- Checkmarks in the table of contentsNow reflect work done in your course ONLY. If students did work in another course their checkmarks do not transfer.
- Registering students via CSV will now validate all of the data before doing the registration
- Lots of bug fixes
Support Runestone
Did you know that over 38,000 students have registered on Runestone Academy since August 1 2020!? At $100 a textbook we have
saved students over $3.8 million! Thats a lot of students and a lot of savings. Please consider a donation
to help pay for server costs and the ongoing development needed to keep runestone online.
A huge Thank You! to those of you who have sent your support already.


Researchers at Google have built a model that takes a high resolution image of prostate tissue and predicts the severity of cancer present. It does this by splitting the image into thousands of tiny square patches and assigning each a Gleason pattern:
To explore the use of model assistance in pathology, pathologists use a fullscreen version of this interface while grading tissue slides. Patches with the same pattern are grouped together and given a colored outline.
This works well for pathologists; seeing the tissue is crucial and the region outlines don’t obscure the underlying histology too much. But it’s missing a key piece of information: how confident the model is in its predictions in different areas of the slide.
Underlying the Gleason pattern prediction for each patch are the model softmax value outputs. Each of the four patterns has a softmax value, representing the probability that the patch is that pattern. A patch with softmax values
The machine learning models make different kinds of mistakes than humans. If pathologists know when to override the model and when to trust it, the human-model combination will be more accurate than either acting alone. This blog post describes the iterative process of designing an interface to show uncertainty—the tradeoffs between information density and legibility; the gap between the design and experience of use; and the impact small adjustments can have on the effectiveness of a visualization.
Here, each patch is colored based on the class of its argmax (the highest softmax value and the model’s prediction for that patch). On the left, the magnitude of the argmax determines the size of each patch; smaller squares surrounded by more white space indicate more uncertainty. On the right example, patches where the magnitude of the argmax is lower and uncertainty is higher are tinted white.
To see the tissue, pathologists could press a button to toggle the confidence overlay. They found the tinted squares easier to read; zooming changes the white space between the sized squares and adds aliasing artifacts.
One disadvantage of tinting is that comparing uncertainty between classes is difficult. A legend and non-RGB color space would alleviate some of this, but size is always going to be a more exact channel.
Along with the model’s certainty in its top prediction, the softmax values also tell us the model’s second best guess. In areas where the model wasn’t confident, pathologists were especially interested in what alternatives the model was considering. If the model’s second guess matched their initial read of the slide, they trusted the model when reading subsequent slides.
The two most likely classes are now shown. In the left example, patches are colored by interpolating between the top two class colors using the ratio of their softmax values. On the right, the top classes are shown as two overlaid squares. The color of the argmax is used as the background and a square with the color of the second class, sized proportional to the ratio, is overlaid.
I initially preferred interpolating between colors—smoother transitions between classes more closely match my intuition for how tissue transitions between Gleason patterns—but there’s a problem in the bottom right of the slide.
In areas where there are three classes close in probability, color interpolation creates discontinuities that are difficult to reason about.
There’s still a discontinuity with two overlaid squares, but it’s easier to understand than mixed colors, which get read by our visual system in a single channel.
Not all discontinuities are bad. The model counts the number of patches with each argmax to grade the entire slide; in this context swapping the order of the squares usefully demarcates the top prediction.
We also have the probabilities for the model’s third and fourth choices.
Each patch has a small stacked bar chart drawn in it, with the height of each class color showing its softmax value.
Zoomed in, this creates a nice effect; you can see there’s a spot that the model thinks is
But pathologists weren't impressed. Zoomed out, there are aliasing artifacts and zoomed in, there’s almost too much information to parse. One pathologist described it as “nauseating”; they’re looking at these slides all day and want something more visually appealing.
I loaded two versions of the model and drew two bar charts in each patch. The bars on the left side of the patch show an earlier run of the model.
Using opacity to highlight places where the argmax differs between the models pulls out the most important information. On the left side of the slide, for example, it’s easy to see that the model switched from predicting
Like highlighting, showing less information can increase clarity. Above, each patch has a slope chart showing the change in percent chance of tumor between two runs of the model. Color also encodes change (purple shows places where the model now thinks tumorous cells are more likely), so it’s readable at multiple zoom levels.
An even simpler approach is also useful–the tinted argmax overlaid with an expert pathologist’s annotations. This helps verify the model is working and highlights regions for improvement.
After interviewing pathologists, it seemed like showing the top two classes as overlaid squares struck the best balance between providing useful information without being overwhelming. Wanting to squeeze just a little bit more information in (the top two squares only encode the ratio between the top two classes, so
The idea seemed elegant in my head, but created lots of visually noisy “L” shapes in practice.
I tried simplifying by only stacking bars instead of boxes, but that ended up being basically equivalent to the stacked bars showing all four classes.
To keep everything in a uniform grid while displaying more than one bit of information per patch, I rounded the softmax values off to quarters and drew four tiny squares on each patch.
This shows about as much model information as is useful for pathologists while avoiding the overload that comes with showing every 5% or 8% prediction.
Using the sort order of the four squares in each patch to encode the argmax—it’s always upper left—brings small shifts in probabilities into focus, but the banding is overwhelming.
Pathologists like playing around with these interfaces to get a sense of how the model thinks, but were skeptical they’d use them in their daily work. Grading a slide requires looking at tissue, which is covered up by the confidence overlay.
To show tissue and uncertainty at the same time, I experimented with contours. These topographical map-style outlines leave most of the tissue exposed.
Unfortunately, they get unreadable when different classes overlap with each other.
Separate contours for each class could work, but I don’t think it would improve much on a simpler small multiple display showing the softmax for each pattern.
Replacing contour outlines with filled shapes clears up the messy overlaps.
Pathologists also liked the appearance of the filled contours (they matched their mental model of smooth transitions between patterns. And turning down the opacity of
There aren’t enough pixels to show each patch’s softmax values and maintain tissue visibility while zoomed out. By aggregating patches based on the zoom level within circles, the uncertainty of different sections of the slide is shown while not totally obscuring the tissue.
I was initially optimistic about this display: it could replace the argmax outlines of the model’s predictions! But the pies don’t nicely cohere in the same way an outline does and reading the slide requires lots of conscious effort.
Pathologists were also confused about the space between the circles. I tried converting the pies to squares and rounding off the aggregated uncertainty to quarters. This made the concept less confusing, but there was even less of a Gestalt effect.
In addition to the zoom level, the visible extent also provides valuable information. While pathologists read the slide like they normally do, the confidence display could update without explicit interaction.
The size of each circle below shows the number of currently visible patches with approximately that softmax value (a half red / half yellow circle represents patches that are about 50% / 50%
Pathologists were confused by this view, frequently asking why circles in the lower left didn’t match the tissue of the lower left of the slide. The force-directed pies might work as part of a triage workflow, helping pick out the most difficult case to grade first.
Each of these provides a nifty thumbprint about the model’s understanding of the slide.
There’s also the position of the pathologist’s mouse. Instead of covering up the whole slide with the top two overlay, an inset shows confidence in the region around the mouse.
Quickly toggling the whole slide confidence overlay is easier to read for experienced users than the inset—you don’t have to look back and forth quite as much—but it is an additional step to perform. Always present in the corner and not requiring intentional interaction, the inset was more approachable for pathologists using the interface for the first time.
Pathologists don’t mind reading slides with region outlines. Can confidence be shown as an outline?
I started by adding a new region type representing
Pathologists missed seeing the model’s second best guess and weren’t sure how to use uncertain areas. I had hoped to try out a workflow where the model graded the “easy” regions and left the unconfident regions for the pathologists to grade, but the uncertain areas weren’t contiguous enough.
For a binary classification task, like marking tissue as either
To show the model’s second best guess, I also tried drawing regions where the model was having trouble deciding between two classes as outlines with two alternating colors.
Again, the noisiness of patch level predictions makes this hard to read.
Instead of trying to cram all this information into a static set of pixels, I tried using animation.
This chart spawns particles based on the softmax values at each patch. Different classes move in different directions, providing some preattentive texture.
Zoomed out, it isn’t immediately apparent that some of the areas in the
Hypothetical outcome plots are another popular way of showing uncertainty. Below, a random class is drawn from the softmax distribution at each patch every frame.
Unfortunately, this isn’t a real hypothetical outcome plot; if a given patch is benign, its neighbors are more likely to be
The current design of the model only outputs softmax values for individual patches without indicating their correlation, making it difficult to sample from the distribution of possible patches. Why not let the pathologists do the sampling themselves?
Mousing over the heatmap reweights the softmax values. Moving
To ease them into this idea of slide-wide uncertainty, I broke the continuous space into nine separate calibrations and asked each pathologist to think of them as nine expert opinions. They’re used to dealing with differing diagnoses; even getting concordant grading from experts to train and evaluate the model on is surprisingly difficult!
Each of the calibration weights are represented by a small bar chart showing the percent of tissue covered by each pattern.
Grouping the calibrations by their Gleason grade gives a good sense of slide-wide uncertainty. Here the model predicts more
There’s also a static version of this idea, overlaying sketchy versions of the calibration weights.
Non-blocky shapes were a positive, but it was hard to read the slide underneath all the lines. The most interesting places, where the model is uncertain and adjusting the calibration moves the argmax boundaries, are the hardest to read because they’re covered in squiggles.
Do these techniques work with other data? In 2015, DNAInfoNYC asked thousands of readers to draw the outline of their neighborhood. As with the prostate slide, there are uncertain boundaries and underlying tissue/streets.
The sketchy outlines work naturally; here each outline is one person’s drawing of a neighborhood.
I thought some of the patch-based techniques might help answer where, exactly, the line betweenBut they’re not that compelling compared to outlines. Neighborhoods are more contiguous than potential tumors. They usually have well defined centers (the borders of Astoria are fuzzy, but everyone agrees on the middle bit) and don’t manifest as chunks that have a 20% chance of existing. The loss of resolution also hurts more; streets are meaningful and don’t align with the grid.
The patch-level uncertainty is noisy and emphasizes the borders between argmax regions. This accurately represents the model’s output, but the exact location of the switch between
Currently, our designs have explored patch-level uncertainty and slide-wide uncertainty. When pathologists talk about uncertainty, though, they refer to regions and glands: “That area looks like it could be
Generating confidence visualizations for such a model or for other types of tissue will require tweaks to the techniques presented here. Small differences change the effectiveness of visualizations in unexpected ways. Switching from four classes to two classes made
Adam Pearce // February 2020
Ben Wedin, Carrie Cai, Davis Foote, Dave Steiner, Emily Reif, Jimbo Wilson, Kunal Nagpal, Fernanda Viegas, Martin Wattenberg, Michael Terry, Pan-Pan Jiang, Rory Sayres, Samantha Winter and Zan Armstrong made this work possible and had many helpful comments.


AbstractResultSet
abstract class AbstractResultSet implements Iterator, ResultSetInterface
Constants
| TYPE_ARRAYOBJECT |
|
| TYPE_ARRAY |
|
Methods
Constructor
Get the row object prototype
Get the return type to use when returning objects from the set
No description
No description
Get the data source used to create the result set
Field terminology is more correct as information coming back from the database might be a column, and/or the result of an operation or intersection of some data
Iterator: move pointer to next item
Iterator: retrieve current key
Iterator: get current item
Iterator: is pointer valid?
Iterator: rewind
Countable: return count of rows
Cast result set to array of arrays
Details
at line 54
__construct(ResultSet $resultSet, string $returnType = self::TYPE_ARRAYOBJECT, null|ArrayObject $arrayObjectPrototype = null)
Constructor
at line 70
AbstractResultSet
setArrayObjectPrototype(ArrayObject $arrayObjectPrototype)
Set the row object prototype
at line 81
ArrayObject
getArrayObjectPrototype()
Get the row object prototype
at line 91
string
getReturnType()
Get the return type to use when returning objects from the set
at line 101
AbstractResultSet
buffer()
at line 112
boolean
isBuffered()
at line 122
null|Iterator
getDataSource()
Get the data source used to create the result set
at line 132
int
getFieldCount()
Field terminology is more correct as information coming back from the database might be a column, and/or the result of an operation or intersection of some data
at line 142
void
next()
Iterator: move pointer to next item
at line 152
mixed
key()
Iterator: retrieve current key
at line 162
array
current()
Iterator: get current item
at line 172
bool
valid()
Iterator: is pointer valid?
at line 182
void
rewind()
Iterator: rewind
at line 192
int
count()
Countable: return count of rows
at line 203
array
toArray()
Cast result set to array of arrays


Once you have a fully built model container, deploying it as
a REST service so you can serve predictions on the web is as
simple as calling model$predict
on your incoming stream of single row data points representing
customers, leads, emails, or whatever else you were modeling for.
The current release of the modeling engine does not include deployment tools out-of-the-box, but it should be straightforward for any engineering teams to build some using HTTP server packages like microserver or Rserve.
See the Syberia roadmap to learn when deployment tools will be released into the modeling engine (or beat us to the punch!).