Class CLCapabilities
- java.lang.Object
-
- org.lwjgl.opencl.CLCapabilities
-
public class CLCapabilities extends java.lang.Object
Defines the capabilities of an OpenCL platform or device.The instance returned by
CLPlatform#createCapabilities
exposes the functionality present on either the platform or any of its devices. This is unlike theCL10.CL_PLATFORM_EXTENSIONS
string, which returns only platform functionality, supported across all platform devices.The instance returned by
CLDevice#createCapabilities
exposes only the functionality available on that particular device.
-
-
Field Summary
-
-
-
Field Detail
-
clBuildProgram
public final long clBuildProgram
-
clCloneKernel
public final long clCloneKernel
-
clCompileProgram
public final long clCompileProgram
-
clCreateAcceleratorINTEL
public final long clCreateAcceleratorINTEL
-
clCreateBuffer
public final long clCreateBuffer
-
clCreateCommandQueue
public final long clCreateCommandQueue
-
clCreateCommandQueueWithProperties
public final long clCreateCommandQueueWithProperties
-
clCreateCommandQueueWithPropertiesAPPLE
public final long clCreateCommandQueueWithPropertiesAPPLE
-
clCreateContext
public final long clCreateContext
-
clCreateContextFromType
public final long clCreateContextFromType
-
clCreateEventFromEGLSyncKHR
public final long clCreateEventFromEGLSyncKHR
-
clCreateEventFromGLsyncKHR
public final long clCreateEventFromGLsyncKHR
-
clCreateFromEGLImageKHR
public final long clCreateFromEGLImageKHR
-
clCreateFromGLBuffer
public final long clCreateFromGLBuffer
-
clCreateFromGLRenderbuffer
public final long clCreateFromGLRenderbuffer
-
clCreateFromGLTexture
public final long clCreateFromGLTexture
-
clCreateFromGLTexture2D
public final long clCreateFromGLTexture2D
-
clCreateFromGLTexture3D
public final long clCreateFromGLTexture3D
-
clCreateFromVA_APIMediaSurfaceINTEL
public final long clCreateFromVA_APIMediaSurfaceINTEL
-
clCreateImage
public final long clCreateImage
-
clCreateImage2D
public final long clCreateImage2D
-
clCreateImage3D
public final long clCreateImage3D
-
clCreateKernel
public final long clCreateKernel
-
clCreateKernelsInProgram
public final long clCreateKernelsInProgram
-
clCreatePipe
public final long clCreatePipe
-
clCreateProgramWithBinary
public final long clCreateProgramWithBinary
-
clCreateProgramWithBuiltInKernels
public final long clCreateProgramWithBuiltInKernels
-
clCreateProgramWithIL
public final long clCreateProgramWithIL
-
clCreateProgramWithSource
public final long clCreateProgramWithSource
-
clCreateSampler
public final long clCreateSampler
-
clCreateSamplerWithProperties
public final long clCreateSamplerWithProperties
-
clCreateSubBuffer
public final long clCreateSubBuffer
-
clCreateSubDevices
public final long clCreateSubDevices
-
clCreateSubDevicesEXT
public final long clCreateSubDevicesEXT
-
clCreateUserEvent
public final long clCreateUserEvent
-
clEnqueueAcquireEGLObjectsKHR
public final long clEnqueueAcquireEGLObjectsKHR
-
clEnqueueAcquireGLObjects
public final long clEnqueueAcquireGLObjects
-
clEnqueueAcquireVA_APIMediaSurfacesINTEL
public final long clEnqueueAcquireVA_APIMediaSurfacesINTEL
-
clEnqueueBarrier
public final long clEnqueueBarrier
-
clEnqueueBarrierWithWaitList
public final long clEnqueueBarrierWithWaitList
-
clEnqueueCopyBuffer
public final long clEnqueueCopyBuffer
-
clEnqueueCopyBufferRect
public final long clEnqueueCopyBufferRect
-
clEnqueueCopyBufferToImage
public final long clEnqueueCopyBufferToImage
-
clEnqueueCopyImage
public final long clEnqueueCopyImage
-
clEnqueueCopyImageToBuffer
public final long clEnqueueCopyImageToBuffer
-
clEnqueueFillBuffer
public final long clEnqueueFillBuffer
-
clEnqueueFillImage
public final long clEnqueueFillImage
-
clEnqueueMakeBuffersResidentAMD
public final long clEnqueueMakeBuffersResidentAMD
-
clEnqueueMapBuffer
public final long clEnqueueMapBuffer
-
clEnqueueMapImage
public final long clEnqueueMapImage
-
clEnqueueMarker
public final long clEnqueueMarker
-
clEnqueueMarkerWithWaitList
public final long clEnqueueMarkerWithWaitList
-
clEnqueueMigrateMemObjectEXT
public final long clEnqueueMigrateMemObjectEXT
-
clEnqueueMigrateMemObjects
public final long clEnqueueMigrateMemObjects
-
clEnqueueNDRangeKernel
public final long clEnqueueNDRangeKernel
-
clEnqueueNativeKernel
public final long clEnqueueNativeKernel
-
clEnqueueReadBuffer
public final long clEnqueueReadBuffer
-
clEnqueueReadBufferRect
public final long clEnqueueReadBufferRect
-
clEnqueueReadImage
public final long clEnqueueReadImage
-
clEnqueueReleaseEGLObjectsKHR
public final long clEnqueueReleaseEGLObjectsKHR
-
clEnqueueReleaseGLObjects
public final long clEnqueueReleaseGLObjects
-
clEnqueueReleaseVA_APIMediaSurfacesINTEL
public final long clEnqueueReleaseVA_APIMediaSurfacesINTEL
-
clEnqueueSVMFree
public final long clEnqueueSVMFree
-
clEnqueueSVMMap
public final long clEnqueueSVMMap
-
clEnqueueSVMMemFill
public final long clEnqueueSVMMemFill
-
clEnqueueSVMMemcpy
public final long clEnqueueSVMMemcpy
-
clEnqueueSVMMigrateMem
public final long clEnqueueSVMMigrateMem
-
clEnqueueSVMUnmap
public final long clEnqueueSVMUnmap
-
clEnqueueTask
public final long clEnqueueTask
-
clEnqueueUnmapMemObject
public final long clEnqueueUnmapMemObject
-
clEnqueueWaitForEvents
public final long clEnqueueWaitForEvents
-
clEnqueueWaitSignalAMD
public final long clEnqueueWaitSignalAMD
-
clEnqueueWriteBuffer
public final long clEnqueueWriteBuffer
-
clEnqueueWriteBufferRect
public final long clEnqueueWriteBufferRect
-
clEnqueueWriteImage
public final long clEnqueueWriteImage
-
clEnqueueWriteSignalAMD
public final long clEnqueueWriteSignalAMD
-
clFinish
public final long clFinish
-
clFlush
public final long clFlush
-
clGetAcceleratorInfoINTEL
public final long clGetAcceleratorInfoINTEL
-
clGetCommandQueueInfo
public final long clGetCommandQueueInfo
-
clGetContextInfo
public final long clGetContextInfo
-
clGetDeviceAndHostTimer
public final long clGetDeviceAndHostTimer
-
clGetDeviceIDs
public final long clGetDeviceIDs
-
clGetDeviceIDsFromVA_APIMediaAdapterINTEL
public final long clGetDeviceIDsFromVA_APIMediaAdapterINTEL
-
clGetDeviceImageInfoQCOM
public final long clGetDeviceImageInfoQCOM
-
clGetDeviceInfo
public final long clGetDeviceInfo
-
clGetEventInfo
public final long clGetEventInfo
-
clGetEventProfilingInfo
public final long clGetEventProfilingInfo
-
clGetExtensionFunctionAddress
public final long clGetExtensionFunctionAddress
-
clGetExtensionFunctionAddressForPlatform
public final long clGetExtensionFunctionAddressForPlatform
-
clGetGLContextInfoAPPLE
public final long clGetGLContextInfoAPPLE
-
clGetGLContextInfoKHR
public final long clGetGLContextInfoKHR
-
clGetGLObjectInfo
public final long clGetGLObjectInfo
-
clGetGLTextureInfo
public final long clGetGLTextureInfo
-
clGetHostTimer
public final long clGetHostTimer
-
clGetImageInfo
public final long clGetImageInfo
-
clGetKernelArgInfo
public final long clGetKernelArgInfo
-
clGetKernelInfo
public final long clGetKernelInfo
-
clGetKernelSubGroupInfo
public final long clGetKernelSubGroupInfo
-
clGetKernelSubGroupInfoKHR
public final long clGetKernelSubGroupInfoKHR
-
clGetKernelWorkGroupInfo
public final long clGetKernelWorkGroupInfo
-
clGetMemObjectInfo
public final long clGetMemObjectInfo
-
clGetPipeInfo
public final long clGetPipeInfo
-
clGetPlatformIDs
public final long clGetPlatformIDs
-
clGetPlatformInfo
public final long clGetPlatformInfo
-
clGetProgramBuildInfo
public final long clGetProgramBuildInfo
-
clGetProgramInfo
public final long clGetProgramInfo
-
clGetSamplerInfo
public final long clGetSamplerInfo
-
clGetSupportedImageFormats
public final long clGetSupportedImageFormats
-
clLinkProgram
public final long clLinkProgram
-
clLogMessagesToStderrAPPLE
public final long clLogMessagesToStderrAPPLE
-
clLogMessagesToStdoutAPPLE
public final long clLogMessagesToStdoutAPPLE
-
clLogMessagesToSystemLogAPPLE
public final long clLogMessagesToSystemLogAPPLE
-
clReleaseAcceleratorINTEL
public final long clReleaseAcceleratorINTEL
-
clReleaseCommandQueue
public final long clReleaseCommandQueue
-
clReleaseContext
public final long clReleaseContext
-
clReleaseDevice
public final long clReleaseDevice
-
clReleaseDeviceEXT
public final long clReleaseDeviceEXT
-
clReleaseEvent
public final long clReleaseEvent
-
clReleaseKernel
public final long clReleaseKernel
-
clReleaseMemObject
public final long clReleaseMemObject
-
clReleaseProgram
public final long clReleaseProgram
-
clReleaseSampler
public final long clReleaseSampler
-
clReportLiveObjectsAltera
public final long clReportLiveObjectsAltera
-
clRetainAcceleratorINTEL
public final long clRetainAcceleratorINTEL
-
clRetainCommandQueue
public final long clRetainCommandQueue
-
clRetainContext
public final long clRetainContext
-
clRetainDevice
public final long clRetainDevice
-
clRetainDeviceEXT
public final long clRetainDeviceEXT
-
clRetainEvent
public final long clRetainEvent
-
clRetainKernel
public final long clRetainKernel
-
clRetainMemObject
public final long clRetainMemObject
-
clRetainProgram
public final long clRetainProgram
-
clRetainSampler
public final long clRetainSampler
-
clSVMAlloc
public final long clSVMAlloc
-
clSVMFree
public final long clSVMFree
-
clSetDefaultDeviceCommandQueue
public final long clSetDefaultDeviceCommandQueue
-
clSetEventCallback
public final long clSetEventCallback
-
clSetKernelArg
public final long clSetKernelArg
-
clSetKernelArgSVMPointer
public final long clSetKernelArgSVMPointer
-
clSetKernelExecInfo
public final long clSetKernelExecInfo
-
clSetMemObjectDestructorCallback
public final long clSetMemObjectDestructorCallback
-
clSetUserEventStatus
public final long clSetUserEventStatus
-
clTerminateContextKHR
public final long clTerminateContextKHR
-
clTrackLiveObjectsAltera
public final long clTrackLiveObjectsAltera
-
clUnloadCompiler
public final long clUnloadCompiler
-
clUnloadPlatformCompiler
public final long clUnloadPlatformCompiler
-
clWaitForEvents
public final long clWaitForEvents
-
OpenCL10
public final boolean OpenCL10
When true,CL10
is supported.
-
OpenCL10GL
public final boolean OpenCL10GL
When true,CL10GL
is supported.
-
OpenCL11
public final boolean OpenCL11
When true,CL11
is supported.
-
OpenCL12
public final boolean OpenCL12
When true,CL12
is supported.
-
OpenCL12GL
public final boolean OpenCL12GL
When true,CL12GL
is supported.
-
OpenCL20
public final boolean OpenCL20
When true,CL20
is supported.
-
OpenCL21
public final boolean OpenCL21
When true,CL21
is supported.
-
cl_altera_compiler_mode
public final boolean cl_altera_compiler_mode
When true,ALTERACompilerMode
is supported.
-
cl_altera_device_temperature
public final boolean cl_altera_device_temperature
When true,ALTERADeviceTemperature
is supported.
-
cl_altera_live_object_tracking
public final boolean cl_altera_live_object_tracking
When true,ALTERALiveObjectTracking
is supported.
-
cl_amd_bus_addressable_memory
public final boolean cl_amd_bus_addressable_memory
When true,AMDBusAddressableMemory
is supported.
-
cl_amd_compile_options
public final boolean cl_amd_compile_options
When true, the amd_compile_options extension is supported.This extension adds the following options, which are not part of the OpenCL specification:
- -g – This is an experimental feature that lets you use the GNU project debugger, GDB, to debug kernels on x86 CPUs running Linux or cygwin/minGW under Windows. This option does not affect the default optimization of the OpenCL code.
- -O0 – Specifies to the compiler not to optimize. This is equivalent to the OpenCL standard option -cl-opt-disable.
- -f[no-]bin-source – Does [not] generate OpenCL source in the .source section. By default, the source is NOT generated.
- -f[no-]bin-llvmir – Does [not] generate LLVM IR in the .llvmir section. By default, LLVM IR IS generated.
- -f[no-]bin-amdil – Does [not] generate AMD IL in the .amdil section. By Default, AMD IL is NOT generated.
- -f[no-]bin-exe – Does [not] generate the executable (ISA) in .text section. By default, the executable IS generated.
- -f[no-]bin-hsail – Does [not] generate HSAIL/BRIG in the binary. By default, HSA IL/BRIG is NOT generated.
To avoid source changes, there are two environment variables that can be used to change CL options during the runtime:
- AMD_OCL_BUILD_OPTIONS – Overrides the CL options specified in
BuildProgram
. - AMD_OCL_BUILD_OPTIONS_APPEND – Appends options to the options specified in
BuildProgram
.
-
cl_amd_device_attribute_query
public final boolean cl_amd_device_attribute_query
When true,AMDDeviceAttributeQuery
is supported.
-
cl_amd_device_board_name
public final boolean cl_amd_device_board_name
When true,AMDDeviceBoardName
is supported.
-
cl_amd_device_persistent_memory
public final boolean cl_amd_device_persistent_memory
When true,AMDDevicePersistentMemory
is supported.
-
cl_amd_device_profiling_timer_offset
public final boolean cl_amd_device_profiling_timer_offset
When true,AMDDeviceProfilingTimerOffset
is supported.
-
cl_amd_device_topology
public final boolean cl_amd_device_topology
When true,AMDDeviceTopology
is supported.
-
cl_amd_event_callback
public final boolean cl_amd_event_callback
When true, the amd_event_callback extension is supported.This extension provides the ability to register event callbacks for states other than
COMPLETE
. The full set of event states are allowed:QUEUED
,SUBMITTED
, andRUNNING
.
-
cl_amd_fp64
public final boolean cl_amd_fp64
When true, the amd_fp64 extension is supported.This extension provides a subset of the functionality of that provided by the cl_khr_fp64 extension. When enabled, the compiler recognizes the double scalar and vector types, compiles expressions involving those types, and accepts calls to all builtin functions enabled by the cl_khr_fp64 extension. However, this extension does not guarantee that all cl_khr_fp64 built in functions are implemented and does not guarantee that the built in functions that have been implemented would be considered conformant to the cl_khr_fp64 extension.
-
cl_amd_media_ops
public final boolean cl_amd_media_ops
When true, the amd_media_ops extension is supported.The directive when enabled adds the following built-in functions to the OpenCL language.
Note: typen denote opencl scalar type {n = 1} and vector types {n = 4, 8, 16}. Build-in Function uint amd_pack(float4 src) Description dst = ((((uint)src.s0) & 0xff) ) + ((((uint)src.s1) & 0xff) << 8) + ((((uint)src.s2) & 0xff) << 16) + ((((uint)src.s3) & 0xff) << 24) Build-in Function floatn amd_unpack3(unitn src) Description dst.s0 = (float)((src.s0 >> 24) & 0xff) similar operation applied to other components of the vectors Build-in Function floatn amd_unpack2 (unitn src) Description dst.s0 = (float)((src.s0 >> 16) & 0xff) similar operation applied to other components of the vectors Build-in Function floatn amd_unpack1 (unitn src) Description dst.s0 = (float)((src.s0 >> 8) & 0xff) similar operation applied to other components of the vectors Build-in Function floatn amd_unpack0 (unitn src) Description dst.s0 = (float)(src.s0 & 0xff) similar operation applied to other components of the vectors Build-in Function uintn amd_bitalign (uintn src0, uintn src1, uintn src2) Description dst.s0 = (uint) (((((long)src0.s0) << 32) | (long)src1.s0) >> (src2.s0 & 31)) similar operation applied to other components of the vectors. Build-in Function uintn amd_bytealign (uintn src0, uintn src1, uintn src2) Description dst.s0 = (uint) (((((long)src0.s0) << 32) | (long)src1.s0) >> ((src2.s0 & 3)*8)) similar operation applied to other components of the vectors Build-in Function uintn amd_lerp (uintn src0, uintn src1, uintn src2) Description dst.s0 = (((((src0.s0 >> 0) & 0xff) + ((src1.s0 >> 0) & 0xff) + ((src2.s0 >> 0) & 1)) >> 1) << 0) + (((((src0.s0 >> 8) & 0xff) + ((src1.s0 >> 8) & 0xff) + ((src2.s0 >> 8) & 1)) >> 1) << 8) + (((((src0.s0 >> 16) & 0xff) + ((src1.s0 >> 16) & 0xff) + ((src2.s0 >> 16) & 1)) >> 1) << 16) + (((((src0.s0 >> 24) & 0xff) + ((src1.s0 >> 24) & 0xff) + ((src2.s0 >> 24) & 1)) >> 1) << 24); similar operation applied to other components of the vectors Build-in Function uintn amd_sad (uintn src0, uintn src1, uintn src2) Description dst.s0 = src2.s0 + abs(((src0.s0 >> 0) & 0xff) - ((src1.s0 >> 0) & 0xff)) + abs(((src0.s0 >> 8) & 0xff) - ((src1.s0 >> 8) & 0xff)) + abs(((src0.s0 >> 16) & 0xff) - ((src1.s0 >> 16) & 0xff)) + abs(((src0.s0 >> 24) & 0xff) - ((src1.s0 >> 24) & 0xff)); similar operation applied to other components of the vectors Build-in Function uintn amd_sadhi (uintn src0, uintn src1n, uintn src2) Description dst.s0 = src2.s0 + (abs(((src0.s0 >> 0) & 0xff) - ((src1.s0 >> 0) & 0xff)) << 16) + (abs(((src0.s0 >> 8) & 0xff) - ((src1.s0 >> 8) & 0xff)) << 16) + (abs(((src0.s0 >> 16) & 0xff) - ((src1.s0 >> 16) & 0xff)) << 16) + (abs(((src0.s0 >> 24) & 0xff) - ((src1.s0 >> 24) & 0xff)) << 16); similar operation applied to other components of the vectors Build-in Function uint amd_sad4(uint4 src0, uint4 src1, uint src2) Description dst = src2 + abs(((src0.s0 >> 0) & 0xff) - ((src1.s0 >> 0) & 0xff)) + abs(((src0.s0 >> 8) & 0xff) - ((src1.s0 >> 8) & 0xff)) + abs(((src0.s0 >> 16) & 0xff) - ((src1.s0 >> 16) & 0xff)) + abs(((src0.s0 >> 24) & 0xff) - ((src1.s0 >> 24) & 0xff)) + abs(((src0.s1 >> 0) & 0xff) - ((src1.s0 >> 0) & 0xff)) + abs(((src0.s1 >> 8) & 0xff) - ((src1.s1 >> 8) & 0xff)) + abs(((src0.s1 >> 16) & 0xff) - ((src1.s1 >> 16) & 0xff)) + abs(((src0.s1 >> 24) & 0xff) - ((src1.s1 >> 24) & 0xff)) + abs(((src0.s2 >> 0) & 0xff) - ((src1.s2 >> 0) & 0xff)) + abs(((src0.s2 >> 8) & 0xff) - ((src1.s2 >> 8) & 0xff)) + abs(((src0.s2 >> 16) & 0xff) - ((src1.s2 >> 16) & 0xff)) + abs(((src0.s2 >> 24) & 0xff) - ((src1.s2 >> 24) & 0xff)) + abs(((src0.s3 >> 0) & 0xff) - ((src1.s3 >> 0) & 0xff)) + abs(((src0.s3 >> 8) & 0xff) - ((src1.s3 >> 8) & 0xff)) + abs(((src0.s3 >> 16) & 0xff) - ((src1.s3 >> 16) & 0xff)) + abs(((src0.s3 >> 24) & 0xff) - ((src1.s3 >> 24) & 0xff));
-
cl_amd_media_ops2
public final boolean cl_amd_media_ops2
When true, the amd_media_ops2 extension is supported.The directive when enabled adds the following built-in functions to the OpenCL language.
Note: typen denote open scalar type { n = 1 } and vector types { n = 2, 4, 8, 16 }. Build-in Function uintn amd_msad (uintn src0, uintn src1, uintn src2) Description uchar4 src0u8 = as_uchar4(src0.s0); uchar4 src1u8 = as_uchar4(src1.s0); dst.s0 = src2.s0 + ((src1u8.s0 == 0) ? 0 : abs(src0u8.s0 - src1u8.s0)) + ((src1u8.s1 == 0) ? 0 : abs(src0u8.s1 - src1u8.s1)) + ((src1u8.s2 == 0) ? 0 : abs(src0u8.s2 - src1u8.s2)) + ((src1u8.s3 == 0) ? 0 : abs(src0u8.s3 - src1u8.s3)); similar operation applied to other components of the vectors Build-in Function ulongn amd_qsad (ulongn src0, uintn src1, ulongn src2) Description uchar8 src0u8 = as_uchar8(src0.s0); ushort4 src2u16 = as_ushort4(src2.s0); ushort4 dstu16; dstu16.s0 = amd_sad(as_uint(src0u8.s0123), src1.s0, src2u16.s0); dstu16.s1 = amd_sad(as_uint(src0u8.s1234), src1.s0, src2u16.s1); dstu16.s2 = amd_sad(as_uint(src0u8.s2345), src1.s0, src2u16.s2); dstu16.s3 = amd_sad(as_uint(src0u8.s3456), src1.s0, src2u16.s3); dst.s0 = as_uint2(dstu16); similar operation applied to other components of the vectors Build-in Function ulongn amd_mqsad (ulongn src0, uintn src1, ulongn src2) Description uchar8 src0u8 = as_uchar8(src0.s0); ushort4 src2u16 = as_ushort4(src2.s0); ushort4 dstu16; dstu16.s0 = amd_msad(as_uint(src0u8.s0123), src1.s0, src2u16.s0); dstu16.s1 = amd_msad(as_uint(src0u8.s1234), src1.s0, src2u16.s1); dstu16.s2 = amd_msad(as_uint(src0u8.s2345), src1.s0, src2u16.s2); dstu16.s3 = amd_msad(as_uint(src0u8.s3456), src1.s0, src2u16.s3); dst.s0 = as_uint2(dstu16); similar operation applied to other components of the vectors Build-in Function uintn amd_sadw (uintn src0, uintn src1, uintn src2) Description ushort2 src0u16 = as_ushort2(src0.s0); ushort2 src1u16 = as_ushort2(src1.s0); dst.s0 = src2.s0 + abs(src0u16.s0 - src1u16.s0) + abs(src0u16.s1 - src1u16.s1); similar operation applied to other components of the vectors Build-in Function uintn amd_sadd (uintn src0, uintn src1, uintn src2) Description dst.s0 = src2.s0 + abs(src0.s0 - src1.s0); similar operation applied to other components of the vectors Built-in Function: uintn amd_bfm (uintn src0, uintn src1) Description dst.s0 = ((1 << (src0.s0 & 0x1f)) - 1) << (src1.s0 & 0x1f); similar operation applied to other components of the vectors Built-in Function: uintn amd_bfe (uintn src0, uintn src1, uintn src2) Description NOTE: operator >> below represent logical right shift offset = src1.s0 & 31; width = src2.s0 & 31; if width = 0 dst.s0 = 0; else if (offset + width) < 32 dst.s0 = (src0.s0 << (32 - offset - width)) >> (32 - width); else dst.s0 = src0.s0 >> offset; similar operation applied to other components of the vectors Built-in Function: intn amd_bfe (intn src0, uintn src1, uintn src2) Description NOTE: operator >> below represent arithmetic right shift offset = src1.s0 & 31; width = src2.s0 & 31; if width = 0 dst.s0 = 0; else if (offset + width) < 32 dst.s0 = src0.s0 << (32-offset-width) >> 32-width; else dst.s0 = src0.s0 >> offset; similar operation applied to other components of the vectors Built-in Function: intn amd_median3 (intn src0, intn src1, intn src2) uintn amd_median3 (uintn src0, uintn src1, uintn src2) floatn amd_median3 (floatn src0, floatn src1, floattn src2) Description returns median of src0, src1, and src2 Built-in Function: intn amd_min3 (intn src0, intn src1, intn src2) uintn amd_min3 (uintn src0, uintn src1, uintn src2) floatn amd_min3 (floatn src0, floatn src1, floattn src2) Description returns min of src0, src1, and src2 Built-in Function: intn amd_max3 (intn src0, intn src1, intn src2) uintn amd_max3 (uintn src0, uintn src1, uintn src2) floatn amd_max3 (floatn src0, floatn src1, floattn src2) Description returns max of src0, src1, and src2
-
cl_amd_offline_devices
public final boolean cl_amd_offline_devices
When true,AMDOfflineDevices
is supported.
-
cl_amd_popcnt
public final boolean cl_amd_popcnt
When true, the amd_popcnt extension is supported.This extension introduces a “population count” function called popcnt. This extension was taken into core OpenCL 1.2, and the function was renamed popcount. The core 1.2 popcount function is identical to the AMD extension popcnt function.
-
cl_amd_predefined_macros
public final boolean cl_amd_predefined_macros
When true, the amd_predefined_macros extension is supported.The following macros are predefined when compiling OpenCL™ C kernels. These macros are defined automatically based on the device for which the code is being compiled.
GPU devices
- __Barts__
- __BeaverCreek__
- __Bheem__
- __Bonaire__
- __Caicos__
- __Capeverde__
- __Carrizo__
- __Cayman__
- __Cedar__
- __Cypress__
- __Devastator__
- __Hainan__
- __Iceland__
- __Juniper__
- __Kalindi__
- __Kauai__
- __Lombok__
- __Loveland__
- __Mullins__
- __Oland__
- __Pitcairn__
- __RV710__
- __RV730__
- __RV740__
- __RV770__
- __RV790__
- __Redwood__
- __Scrapper__
- __Spectre__
- __Spooky__
- __Tahiti__
- __Tonga__
- __Turks__
- __WinterPark__
- __GPU__
CPU devices
- __CPU__
- __X86__
- __X86_64__
Note that __GPU__ or __CPU__ are predefined whenever a GPU or CPU device is the compilation target.
-
cl_amd_printf
public final boolean cl_amd_printf
When true, the amd_printf extension is supported.This extension adds the built-in function
printf(__constant char * restrict format, …);
This function writes output to the stdout stream associated with the host application. The format string is a character sequence that:
- is null-terminated and composed of zero and more directives,
- ordinary characters (i.e. not %), which are copied directly to the output stream unchanged, and
- conversion specifications, each of which can result in fetching zero or more arguments, converting them, and then writing the final result to the output stream.
The format string must be resolvable at compile time; thus, it cannot be dynamically created by the executing program. (Note that the use of variadic arguments in the built-in printf does not imply its use in other builtins; more importantly, it is not valid to use printf in user-defined functions or kernels.)
The OpenCL C printf closely matches the definition found as part of the C99 standard. Note that conversions introduced in the format string with % are supported with the following guidelines:
- A 32-bit floating point argument is not converted to a 64-bit double, unless the extension cl_khr_fp64 is supported and enabled. This includes the double variants if cl_khr_fp64 is supported and defined in the corresponding compilation unit.
- 64-bit integer types can be printed using %ld / %lx / %lu.
- %lld / %llx / %llu are not supported and reserved for 128-bit integer types (long long).
- All OpenCL vector types can be explicitly passed and printed using the modifier vn, where n can be 2, 3, 4, 8, or 16. This modifier appears before the original conversion specifier for the vector’s component type (for example, to print a float4 %v4f). Since vn is a conversion specifier, it is valid to apply optional flags, such as field width and precision, just as it is when printing the component types. Since a vector is an aggregate type, the comma separator is used between the components: 0:1, … , n-2:n-1.
-
cl_amd_vec3
public final boolean cl_amd_vec3
When true, the amd_vec3 extension is supported.This extension adds support for vectors with three elements: float3, short3, char3, etc. This data type was added to OpenCL 1.1 as a core feature.
-
cl_APPLE_biased_fixed_point_image_formats
public final boolean cl_APPLE_biased_fixed_point_image_formats
When true,APPLEBiasedFixedPointImageFormats
is supported.
-
cl_APPLE_command_queue_priority
public final boolean cl_APPLE_command_queue_priority
When true,APPLECommandQueuePriority
is supported.
-
cl_APPLE_command_queue_select_compute_units
public final boolean cl_APPLE_command_queue_select_compute_units
When true,APPLECommandQueueSelectComputeUnits
is supported.
-
cl_APPLE_ContextLoggingFunctions
public final boolean cl_APPLE_ContextLoggingFunctions
When true,APPLEContextLoggingFunctions
is supported.
-
cl_APPLE_fixed_alpha_channel_orders
public final boolean cl_APPLE_fixed_alpha_channel_orders
When true,APPLEFixedAlphaChannelOrders
is supported.
-
cl_APPLE_fp64_basic_ops
public final boolean cl_APPLE_fp64_basic_ops
When true,APPLE_fp64_basic_ops
is supported.
-
cl_APPLE_gl_sharing
public final boolean cl_APPLE_gl_sharing
When true,APPLEGLSharing
is supported.
-
cl_APPLE_query_kernel_names
public final boolean cl_APPLE_query_kernel_names
When true,APPLEQueryKernelNames
is supported.
-
cl_arm_core_id
public final boolean cl_arm_core_id
When true, the arm_core_id extension is supported.This extension provides a built-in function (
uint arm_get_core_id( void )
) which returns the physical core id (OpenCL Compute Unit) that a work-group is running on. This value is uniform for a work-group.This value can be used for a core-specific cache or atomic pool where the storage is required to be in global memory and persistent (but not ordered) between work-groups. This does not provide any additional ordering on top of the existing guarantees between workgroups, nor does it provide any guarantee of concurrent execution.
-
cl_arm_printf
public final boolean cl_arm_printf
When true,ARMPrintf
is supported.
-
cl_ext_atomic_counters_32
public final boolean cl_ext_atomic_counters_32
When true,EXTAtomicCounters32
is supported.
-
cl_ext_atomic_counters_64
public final boolean cl_ext_atomic_counters_64
When true,EXTAtomicCounters64
is supported.
-
cl_ext_device_fission
public final boolean cl_ext_device_fission
When true,EXTDeviceFission
is supported.
-
cl_ext_migrate_memobject
public final boolean cl_ext_migrate_memobject
When true,EXTMigrateMemobject
is supported.
-
cl_intel_accelerator
public final boolean cl_intel_accelerator
When true,INTELAccelerator
is supported.
-
cl_intel_advanced_motion_estimation
public final boolean cl_intel_advanced_motion_estimation
When true,INTELAdvancedMotionEstimation
is supported.
-
cl_intel_device_partition_by_names
public final boolean cl_intel_device_partition_by_names
When true,INTELDevicePartitionByNames
is supported.
-
cl_intel_egl_image_yuv
public final boolean cl_intel_egl_image_yuv
When true,INTELEGLImageYUV
is supported.
-
cl_intel_motion_estimation
public final boolean cl_intel_motion_estimation
When true,INTELMotionEstimation
is supported.
-
cl_intel_printf
public final boolean cl_intel_printf
When true,intel_printf
is supported.
-
cl_intel_simultaneous_sharing
public final boolean cl_intel_simultaneous_sharing
When true,INTELSimultaneousSharing
is supported.
-
cl_intel_subgroups
public final boolean cl_intel_subgroups
When true,INTELSubgroups
is supported.
-
cl_intel_thread_local_exec
public final boolean cl_intel_thread_local_exec
When true,INTELThreadLocalExec
is supported.
-
cl_intel_va_api_media_sharing
public final boolean cl_intel_va_api_media_sharing
When true,INTELVAAPIMediaSharing
is supported.
-
cl_khr_3d_image_writes
public final boolean cl_khr_3d_image_writes
When true, the khr_3d_image_writes extension is supported.This extension adds support for kernel writes to 3D images.
-
cl_khr_byte_addressable_store
public final boolean cl_khr_byte_addressable_store
When true, the khr_byte_addressable_store extension is supported.This extension eliminates the restriction of not allowing writes to a pointer (or array elements) of types less than 32-bit wide in kernel program.
-
cl_khr_depth_images
public final boolean cl_khr_depth_images
When true,KHRDepthImages
is supported.
-
cl_khr_device_enqueue_local_arg_types
public final boolean cl_khr_device_enqueue_local_arg_types
When true, the khr_device_enqueue_local_arg_types extension is supported.This extension allows arguments to blocks passed to enqueue_kernel functions to be declared as a pointer to any type (built-in or user-defined) in local memory instead of just
local void *
.
-
cl_khr_egl_event
public final boolean cl_khr_egl_event
When true,KHREGLEvent
is supported.
-
cl_khr_egl_image
public final boolean cl_khr_egl_image
When true,KHREGLImage
is supported.
-
cl_khr_fp16
public final boolean cl_khr_fp16
When true,KHRFP16
is supported.
-
cl_khr_fp64
public final boolean cl_khr_fp64
When true,KHRFP64
is supported.
-
cl_khr_gl_depth_images
public final boolean cl_khr_gl_depth_images
When true,KHRGLDepthImages
is supported.
-
cl_khr_gl_event
public final boolean cl_khr_gl_event
When true,KHRGLEvent
is supported.
-
cl_khr_gl_msaa_sharing
public final boolean cl_khr_gl_msaa_sharing
When true,KHRGLMSAASharing
is supported.
-
cl_khr_gl_sharing
public final boolean cl_khr_gl_sharing
When true,KHRGLSharing
is supported.
-
cl_khr_global_int32_base_atomics
public final boolean cl_khr_global_int32_base_atomics
When true, the khr_global_int32_base_atomics extension is supported.This extension adds basic atomic operations on 32-bit integers in global memory.
-
cl_khr_global_int32_extended_atomics
public final boolean cl_khr_global_int32_extended_atomics
When true, the khr_global_int32_extended_atomics extension is supported.This extension adds extended atomic operations on 32-bit integers in global memory.
-
cl_khr_icd
public final boolean cl_khr_icd
When true,KHRICD
is supported.
-
cl_khr_image2d_from_buffer
public final boolean cl_khr_image2d_from_buffer
When true,KHRImage2DFromBuffer
is supported.
-
cl_khr_initialize_memory
public final boolean cl_khr_initialize_memory
When true,KHRInitializeMemory
is supported.
-
cl_khr_int64_base_atomics
public final boolean cl_khr_int64_base_atomics
When true, the khr_int64_base_atomics extension is supported.This extension adds basic atomic operations on 64-bit integers in both global and local memory.
-
cl_khr_int64_extended_atomics
public final boolean cl_khr_int64_extended_atomics
When true, the khr_int64_extended_atomics extension is supported.This extension adds extended atomic operations on 64-bit integers in both global and local memory.
-
cl_khr_local_int32_base_atomics
public final boolean cl_khr_local_int32_base_atomics
When true, the khr_local_int32_base_atomics extension is supported.This extension adds basic atomic operations on 32-bit integers in local memory.
-
cl_khr_local_int32_extended_atomics
public final boolean cl_khr_local_int32_extended_atomics
When true, the khr_local_int32_extended_atomics extension is supported.This extension adds extended atomic operations on 32-bit integers in local memory.
-
cl_khr_mipmap_image
public final boolean cl_khr_mipmap_image
When true,KHRMipmapImage
is supported.
-
cl_khr_mipmap_image_writes
public final boolean cl_khr_mipmap_image_writes
When true, the khr_mipmap_image_writes extension is supported.This extension adds built-in functions that can be used to write a mip-mapped image in an OpenCL C program.
-
cl_khr_priority_hints
public final boolean cl_khr_priority_hints
When true,KHRPriorityHints
is supported.
-
cl_khr_select_fprounding_mode
public final boolean cl_khr_select_fprounding_mode
When true, the khr_select_fprounding_mode extension is supported.This extension adds support for specifying the rounding mode for an instruction or group of instructions in the program source.
The appropriate rounding mode can be specified using
#pragma OPENCL SELECT_ROUNDING_MODE
rounding-mode in the program source.The
#pragma OPENCL SELECT_ROUNDING_MODE
sets the rounding mode for all instructions that operate on floating-point types (scalar or vector types) or produce floating-point values that follow this pragma in the program source until the next#pragma OPENCL SELECT_ROUNDING_MODE
is encountered. Note that the rounding mode specified for a block of code is known at compile time. Except where otherwise documented, the callee functions do not inherit the rounding mode of the caller function.If this extension is enabled, the
__ROUNDING_MODE__
preprocessor symbol shall be defined to be one of the following according to the current rounding mode:#define __ROUNDING_MODE__ rte #define __ROUNDING_MODE__ rtz #define __ROUNDING_MODE__ rtp #define __ROUNDING_MODE__ rtz
The default rounding mode is round to nearest even. The built-in math functions, the common functions, and the geometric functions are implemented with the round to nearest even rounding mode.
Various built-in conversions and the vstore_half and vstorea_halfn built-in functions that do not specify a rounding mode inherit the current rounding mode. Conversions from floating-point to integer type always use rtz mode, except where the user specifically asks for another rounding mode.
Notes The above four rounding modes are defined by IEEE 754. Floating-point calculations may be carried out internally with extra precision and then rounded to fit into the destination type. Round to nearest even is currently the only rounding mode required by the OpenCL specification and is therefore the default rounding mode. In addition, only static selection of rounding mode is supported. Dynamically reconfiguring the rounding modes as specified by the IEEE 754 spec is not a requirement.
-
cl_khr_spir
public final boolean cl_khr_spir
When true,KHRSPIR
is supported.
-
cl_khr_terminate_context
public final boolean cl_khr_terminate_context
When true,KHRTerminateContext
is supported.
-
cl_khr_throttle_hints
public final boolean cl_khr_throttle_hints
When true,KHRThrottleHints
is supported.
-
cl_nv_compiler_options
public final boolean cl_nv_compiler_options
When true, the nv_compiler_options extension is supported.This extension allows the programmer to pass options to the PTX assembler allowing greater control over code generation.
-cl-nv-maxrregcount
Passed on to ptxas as --maxrregcount N is a positive integer. Specify the maximum number of registers that GPU functions can use. Until a function-specific limit, a higher value will generally increase the performance of individual GPU threads that execute this function. However, because thread registers are allocated from a global register pool on each GPU, a higher value of this option will also reduce the maximum thread block size, thereby reducing the amount of thread parallelism. Hence, a good maxrregcount value is the result of a trade-off. If this option is not specified, then no maximum is assumed. Otherwise the specified value will be rounded to the next multiple of 4 registers until the GPU specific maximum of 128 registers. -cl-nv-opt-level Passed on to ptxas as --opt-level N is a positive integer, or 0 (no optimization). Specify optimization level. Default value: 3. -cl-nv-verbose Passed on to ptxas as --verbose Enable verbose mode. Output will be reported in the build log (accessible through the callback parameter to clBuildProgram).
-
cl_nv_device_attribute_query
public final boolean cl_nv_device_attribute_query
When true,NVDeviceAttributeQuery
is supported.
-
cl_nv_pragma_unroll
public final boolean cl_nv_pragma_unroll
When true, the nv_pragma_unroll extension is supported.Overview
This extension extends the OpenCL C language with a hint that allows loops to be unrolled. This pragma must be used for a loop and can be used to specify full unrolling or partial unrolling by a certain amount. This is a hint and the compiler may ignore this pragma for any reason.
Goals
The principal goal of the pragma unroll is to improve the performance of loops via unrolling. Typically this enables other optimizations or improves instruction level parallelism of a thread.
Details
A user may specify that a loop in the source program be unrolled. This is done via a pragma. The syntax of this pragma is as follows
#pragma unroll [unroll-factor]
The pragma unroll may optionally specify an unroll factor. The pragma must be placed immediately before the loop and only applies to that loop.
If unroll factor is not specified then the compiler will try to do complete or full unrolling of the loop. If a loop unroll factor is specified the compiler will perform partial loop unrolling. The loop factor, if specified, must be a compile time non negative integer constant.
A loop unroll factor of 1 means that the compiler should not unroll the loop.
A complete unroll specification has no effect if the trip count of the loop is not compile-time computable.
-
cl_qcom_ext_host_ptr
public final boolean cl_qcom_ext_host_ptr
When true,QCOMEXTHostPtr
is supported.
-
-


{% extends "layout.html" %} {% block page_title %} Where you live {% endblock %} {% block content %} {% include "../includes/phase_banner_beta.html" %} Back Living with parents, relatives or friends Is the property rented? Yes No Who pays the rent?  Who owns the property?


RIPS at IPAM, UCLA - Application and Pre-Intern Experience 2019
Introduction: RIPS Internship
RIPS stands for Research in Industrial Projects for Students. It is an annual research program organised by the Institute of Pure and Applied Mathematics (IPAM) of UCLA. With an acceptance rate of 2-3%, it hosts every year 36 interns who work on 9 industrial projects in groups of 4. I was one of the interns selected for the year 2019 and this post describes my application process and experience. The intern and personal experience will be covered in a separate post.
APPLICATION AND PRE-SELECTION EXPERIENCE:
By the end of September I had secured two on-campus internships at Morgan Stanley and Adobe but something inside me was not satisfied. So I started applying for research internships abroad. It is especially tough in our culture because we don’t have any curated list so refer to this link which contains a non-exhaustive list of internships (some exclusively for Indian students). I was selective when applying for internships because I knew they are highly competitive and anyone having an aggregate CGPA of <9.5 (out of 10) has less chance securing some of them.
Fast forward to February, I was getting frustrated with not getting any results. I remember sitting in the library of IIT-D, waiting for my professor to return from his meeting to wrap up my paper with him. I had a couple of hours and decided to apply for one final intern. It was Research in Industrial Projects for Students, or RIPS, offered by Institute of Pure and Applied Mathematics (IPAM), residing in UCLA. I was interested in applying for it partly because mathematics and CS always appealed to me, and somewhat because I was torn between academia and industry and this internship seemed to be the perfect mix of both. I was also interested because my college senior (who I look up to) secured this internship the previous year and I remember him telling me how great his experience was (great would be an understatement). So there I was, sitting in the library, with my friend from FIITJEE days by my side, stressed and freakishly writing answers for which math and CS courses I had taken, which languages I had worked on (and by what scale) and describing the major projects I had worked on. I wasn’t required to write a Statement of Purpose but was asked to upload my college transcripts and 2 Letter of Recommendations (LORs) from my professors. I sat there for the entire day and filled the form up. I requested my professors to upload a LOR telling IPAM people how I am the best, most passionate and funny person everr! They were happy to (Big shoutout to Dr. Ruchika Malhotra, my guide).
Fast forward to February 28, I had come back from my bitter-sweet conference and had to leave for Kerala to participate in Smart India Hackathon with my awesome team. I woke up at 6 am, and as usual checked my email the first thing in the morning. But unlike most mornings where I only got mails from Grammarly, KDNuggets and Medium, this time I had an email that was titled ‘UCLA RIPS-Summer REU’ from a Dimi. It said they were interested in offering me an intern position at their esteemed RIPS program. I refused to believe. Few hours later, I was in metro with my luggage to board my flight when I opened my laptop and showed my friend the email. He made me believe I was crazy, and I finally accepted what had just happened and replied back.
Finally in second week of March (a night before my Operating Systems mid-term examination), just before I was going to bed, at 12.15 am, I received an email that said ‘RIPS LA 2019 Offer Letter’ and I remember going to my friends in adjacent room and showing them the email. The next few minutes were about shedding some tears and staying in disbelief. I told my two awesomesauce seniors, mentors and guides, and as always they made me realise how big it was and congratulated me in the best way possible! (In words of one of them: Right now, I am this person who is sitting in a Google meeting room smiling like crazies).
Key takeaways:
- Refer to this link and contribute to it if you find other internships.
- Don’t apply everywhere. Be selective and invest your effort and time only in programs that align with your ideology.
- Don’t stop yourself from applying just because you don’t think you have a shot (Imposter Syndrome). You have a shot. But only if you put yourself out there. Apply.
- Have a good support system, progressive friends and consistent mindset.
- If I can do it, so can you. You got this. Go and apply.
This is the link to RIPS official page. The applicaions open in November and the deadline is February second week.
Hope this was helpful. If you have any other queries regarding the application process, contact me on my email id: shreyagupta_bt2k16 [at] dtu [dot] ac [dot] in
All the best!


Hey! You found a URL on the badge!
Come back later. We will update this page and explain the cool stuff you can do with it.
Yep, you can download it, here. We'll release even more details soon.
The badge exposes a Bluetooth Low Energy (BLE) service that allows you to customize your badge wirelessly. The name and the avatar image can be changed.
The service UUID is 6AA99996-93B3-95BA-BC40-42684CDB36FB
.
Here is a description of the characteristics:
| UUID | Permissions | Size | Description |
|---|---|---|---|
| 6AA96E6D-93B3-95BA-BC40-42684CDB36FB | Read-Write | 14 bytes | The owner name (defaults to Comrade #00000). |
| 6AA96176-93B3-95BA-BC40-42684CDB36FB | Read-Write | 128 bytes | The avatar bitmap, 32x32 pixels at 1 bit per pixel. |
| 6AA96176-93B3-95BA-BC40-42684CDB36FB | Read-Write | 4 bytes | Sync key. Set this to the sync key displayed in the setting menu to "unlock" the badge and allow you to upload a new name and avatar. The badge will relock if you set it to anything else. |
| 6AA96177-93B3-95BA-BC40-42684CDB36FB | Read-only | 1 byte | Set to 1 if badge is unlocked, 0 otherwise |
To create a customize your badge you shall:
"But, I don't want to write code!"
Okay, here is a reference implementation for you. Works on macOS.
nsec17_badge_client.swift Usage:
swift nsec17_badge_client.swift --device NSEC1234 --key 5678 [--name NAME | --avatar BITMAP_FILE]
With the conference firware, the USB port exposes a serial device that act as a gdb stub. It is based on the Black Magic Probe. You can use it to read, write and debug the nRF51 micro controller with only a micro USB cable.
If you have the CTF firmware, you can flash the debugger to the STM32 too. First, you need to remove the protection using the following Python script: stm32-dfu.py. First, put you badge in DFU mode by holding the "program" button and pressing the "reset" button. Then plug you badge in and use:
python stm32-dfu.py unprotect
This will erase the CTF firmware, but allow you to upload a new
firmware. To upload a new firmware, put your badge in DFU mode again and
use dfu-util
,
with the following settings:
dfu-util --reset --device 0483:df11 --alt 0 --dfuse-address 0x08000000 --download FIRMWARE_FILE.bin
The following firmware images are available for the STM32 chip:
Connecting two badges together:
Source code will be available after the event.
More details to come.


Please provide your updated information for visa processing.
Already have an account? Please Login
Back to Sign Up


sBltAddFade performs additive-blending transfer, while attenuating the source intensity.
void sBltAddFade(long x,long y,long wid,long hei,long x2,long y2,long Fader);
None. [ASM: All registers are preserved.]
sBltAddFade(0,0,400,300,0,0,161);
3-4 times slower than sBltAdd.


DESCRIPTION:
Nokogiri (鋸) is an HTML, XML, SAX, and Reader parser. Among Nokogiri’s many features is the ability to search documents via XPath or CSS3 selectors.
XML is like violence - if it doesn’t solve your problems, you are not using enough of it.
FEATURES:
-
XPath support for document searching
-
CSS3 selector support for document searching
-
XML/HTML builder
Nokogiri parses and searches XML/HTML very quickly, and also has correctly implemented CSS3 selector support as well as XPath support.
SUPPORT:
The Nokogiri mailing list is available here:
* http://groups.google.com/group/nokogiri-talk
The bug tracker is available here:
* http://github.com/tenderlove/nokogiri/issues
The IRC channel is nokogiri on freenode.
SYNOPSIS:
require 'nokogiri' require 'open-uri' # Get a Nokogiri::HTML:Document for the page we’re interested in... doc = Nokogiri::HTML(open('http://www.google.com/search?q=tenderlove')) # Do funky things with it using Nokogiri::XML::Node methods... #### # Search for nodes by css doc.css('h3.r a.l').each do |link| puts link.content end #### # Search for nodes by xpath doc.xpath('//h3/a[@class="l"]').each do |link| puts link.content end #### # Or mix and match. doc.search('h3.r a.l', '//h3/a[@class="l"]').each do |link| puts link.content end
REQUIREMENTS:
-
ruby 1.8 or 1.9
-
libxml2
-
libxml2-dev
-
libxslt
-
libxslt-dev
ENCODING:
Strings are always stored as UTF-8 internally. Methods that return text values will always return UTF-8 encoded strings. Methods that return XML (like to_xml, to_html and inner_html) will return a string encoded like the source document.
WARNING
Some documents declare one particular encoding, but use a different one. So, which encoding should the parser choose?
Remember that data is just a stream of bytes. Only us humans add meaning to that stream. Any particular set of bytes could be valid characters in multiple encodings, so detecting encoding with 100% accuracy is not possible. libxml2 does its best, but it can’t be right 100% of the time.
If you want Nokogiri to handle the document encoding properly, your best bet is to explicitly set the encoding. Here is an example of explicitly setting the encoding to EUC-JP on the parser:
doc = Nokogiri.XML('<foo><bar /><foo>', nil, 'EUC-JP')
INSTALL:
-
sudo gem install nokogiri
Binary packages
Binary packages are available for:
DEVELOPMENT:
Developing on C Ruby (MRI)
Developing Nokogiri requires racc and rexical to generate the parser and tokenizer. To start development, make sure you have `libxml2` and `libxslt` installed.
Then install hoe and rake-compiler:
$ gem install hoe rake-compiler racc rexical minitest
Then run rake:
$ rake
Developing on JRuby
Currently, development with JRuby depends on C Ruby being installed. With normal C Ruby, install racc and rexical:
$ gem install racc rexical
Make sure hoe and rake compiler are installed with JRuby:
$ jgem install hoe rake-compiler
Then run rake:
$ jruby -S rake
LICENSE:
(The MIT License)
Copyright © 2008 - 2010:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ‘Software’), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


All Cycles
FAQ
Stacks is an open-source network of decentralized apps and smart contracts built on Bitcoin. Stacks unleashes Bitcoin's full potential as a programmable base layer. They run their logic on the blockchain with smart contracts, are controlled by code instead of companies, and are accessible to anyone.
Earn Bitcoin by Stacking
Lock your STX temporarily to support the network’s security and consensus. As a reward, you’ll earn Bitcoin that miners transfer as part of Proof of Transfer.
Reimagine our financial system on Bitcoin
Stacks makes Bitcoin's $760B of capital programmable with smart contracts. Build a better financial system on top of Bitcoin that’s open, composable, and without intermediaries.
Clarity, for safer smart contracts
Run your app’s logic on the blockchain with Clarity smart contracts. Clarity is a more secure and predictable language that prevents many bugs and exploits. Perfect for high-stakes code where bugs are not an option.
To learn more about Stacks please visit Stacks website
There are two ways to stack: by yourself or in a pool. To stack by yourself you’ll
need to meet the dynamic minimum, which can change from cycle to cycle. If you don’t
meet the minimum, you can still stack by pooling with others.
Read the stacking guide to
choose a strategy that's right for you.
Even if you don't meet the minimum, you can still stack and earn Bitcoin by pooling
with others. A service will pool STX together and distribute rewards back to the
participants.
If you want to stack in a pool and see to pool list, please click here.
All data and information is provided "as is" for informational purposes only and is not for trading or advice on financial, investment, tax, legal, accounting or other matters. Please check with your broker or financial representative to verify prices prior to any trading.


Welcome to Dirt-Finder
Dirt-Finder is a site completely dedicated to streamlining the import and export of soil from jobsites.
Simply create and account, click on the Have Dirt/Need Dirt Tab and enter the jobsite info.
This will post a pin to the map that will show others where your jobsite is and will allow them to click on your tab and find your contact information.
- Have Dirt
- Need Dirt


MYST Asian Fusion
taste the difference
Menu
Appetizers - Marinated items
香辣牛肉乾拌麵 - $11.95
Contact and Hours
(604) - 364 - 6400
10am to 1 am, Monday to Sunday
Where are we?


Come join this crazy group of fun, loving college students as we hang out and get to meet new people! And the fun doesn't stop after club, because everyone goes to the local Cookout or Krispy Kreme afterwards.
Important Dates, Times, and Locations!
Fall Weekend
Dates: September 23-24, 2017
Location: Rockbridge, VA
Weekly Club
Dates: Every Tuesday night at 8:48pm
Location: Whitehurst Living Room (Subject to Change)


Lucy E Delaney | University of Illinois at Chicago
This page is no longer active!
Come find me at
my new spot:
https://ledelaney.org
RIP this page 12 Jan 2021


{{flight.takeOffDate | date: 'dd-MM-yyyy'}}
Airline:{{flight.airlineName}}
From:{{flight.from}}
To:{{flight.to}}
Departure:{{flight.takeOffTime}}
{{flight.flightTime}} Arrival:{{flight.landingTime}}
Flight:{{flight.flightNumber}}
Distance:{{flight.flightLength}}km
Seat:{{seatName.class}}{{seatName.column}}{{seatName.row}}
{{stop.city}}
{{stop.city}},
Rate airline
Rate airline
Rate it from 1 to 5{{rateAirline}}
You've already rated this airline!
Rate flight
Rate flight
Rate it from 1 to 5{{rateFlight}}
You've already rated this flight!


If you requested this URL on port 8000 locally, this container is configured properly.
If you requested this URL on port 80 of an upstream server, this container is deployed properly.


Delhi HC Orders DU's School of Open Learning to Postpones First Semester Exams to Next Year
After hearing a petition filed by students, the Delhi High Court has ordered the Delhi University to conduct the first-semester exam along with the second-semester exam in the following year.
New Delhi: Upon the order of the Delhi High court, the Delhi University has postponed the first semester School of Open Learning (SOL) examinations to May-June 2020, on the dates fixed for the second-semester exams, stated a report.
Initially, the first-semester exams were scheduled to be conducted in November-December 2019. However, as per the Delhi High Court order dated November 21, the first semester exams will be held in May-June next year. The SOL has also released an official notification in this regard on Monday.
The HC order was based on the hearing of a plea filed by students seeking the implementation of the semester system from 2020, stated news agency PTI.
The institute has also formed a committee to examine the grievances of the students and to suggest remedies.
The students have been agitating against the implementation of the Choice Based Credit System (CBCS) in SOL after the varsity took a decision in August.
Under the CBCS, the school of open learning was asked to switch from annual mode to semester mode to bring it on par with other DU colleges.
Harish Gautam, a third year student of SOL and a member of Krantikari Yuva Sangathan (KYS), welcomed the notification.
The KYS has been a frontrunner in demanding that the semester mode be implemented from next year to allow more time for students to get acquainted with the system.
(With inputs from PTI)
For breaking news and live news updates, like us on Facebook or follow us on Twitter and Instagram. Read more on Exams & Results Latest News on India.com.
Story Timeline
- 01 Oct 2019 DU BA, BCom Exam 2019: Delhi University Declares Results of School of Open Learning Programmes at sol.du.ac.in
- 02 Jul 2019 DU Admissions 2019: Delhi University Takes Over 23,000 Students in First Cut-Off List
- 30 Jun 2019 Kiara Advani Feels Nostalgic as She Visits Delhi University For Another Film's Shoot Post Kabir Singh
- 13 Jun 2019 DU Admission 2019: List of Documents Required For Delhi University Registration Process; Read to Know More
- 02 Jun 2019 Delhi University Mulls Over Giving Full Scholarships to Orphans or Students Whose Parents Are Unemployed
Comments - Join the Discussion


This screen provides advanced features that primarily only the website administrator for Bioimages will have use for.
A function is provided to resize the full-size images down to the various resolutions used on the Bioimages website. When resized to thumbnails (tn) the larger image dimension is scaled down to 100 pixels, low quality (lq) images are scaled down to 480 pixels, and good quality (gq) images down to 1024 pixels.
The namespace is the name of the folder that the images will reside in on the Bioimages server. Typically it is the agent ID of the photographer or their organization's ID. When images are resized they will be saved to the following folders: <base_output_directory>/tn/<namespace>/, <base_output_directory>/lq/<namespace>/, and <base_output_directory>/gq/<namespace>/.
Generation of the website from the metadata records is now handled by XQuery scripts available at https://github.com/baskaufs/Bioimages.


A list of pets below:
The cat is a small carnivorous mammal. It is the only domesticated species in the family Felidae and often referred to as the domestic cat to distinguish it from wild members of the family.
below is a list of a cat's favorite toys
The domestic dog is a member of the genus Canis, which forms part of the wolf-like canids, and is the most widely abundant terrestrial carnivore.
below is alist of dog's favorite toys


{% extends 'KPS_app/bootstrap.html' %} {% load url from future %} {% load bootstrap3 %} {% block bootstrap3_content %}
This example is a quick exercise to illustrate how the default, static navbar and fixed to top navbar work. It includes the responsive CSS and HTML, so it also adapts to your viewport and device.
{% endblock %}


For weeks I have been trying to get my hands on some acid or some shrooms (neither of which have I had the pleasure of trying) and I was getting frustrated with my dealers from whom I had been promised both substances. I have been a long time pothead, drink quite frequently and tuss every once in a while so besides the tuss I have had no experience with hallucinogens. Since I was frustrated about not getting to experience the exciting and pleasurable trips my friends always raved about and since I had been detained by my parents for the night I decided I'd get as fucked up as I could. My dad rented movies and I figured this would be a decent time to do it. I had been reading about benadryl and how it makes people see people that aren't really there and other crazy visuals like that so I was a bit wary to try it in front of my parents but I figured what the hell and just limited my dose. Here's how it went:
(T+0:00) Popped five of the 25 mg pills, went down to begin watching the first movie, Envy, with Ben Stiller and Jack Black which I figured must be hilarious.
 Popped three more pills.
(T+0:40) Beginning to feel a real heaviness about my whole body. I had read that benadryl makes people extremely tired so I decided to pop a few caffeine pills as well - good idea as I would have passed out early if I hadn't have done this.
(T+1:00) Still just feeling really heavy, but no visuals. Kind of disappointing so I go to pop a few more. Pop two more pills and join the 'rents back in the basement.
(T+1:30) Nothing much different until now.  Whenever I move myself on the couch it takes great force to move even the smallest distance.  I feel really drunk and stoned yet much heavier and without the euphoria of being high. I feel like I have moved to another planet where gravity is about ten times as strong as on Earth. Picking up my glass of water on a table about only a foot and a half away is very difficult. I had to focus all of my energy on this task. It was actually quite interesting to move as the effects of this drug felt greatly intensified with all movement, I was having a good time although the movie was absolutely horrible.
(T+1:50) That God awful movie is over. I have to put in the next one and this requires quite a bit of movement, in front of my parents nonetheless. I am able to concentrate enough to counteract the wooziness, but I feel like I am in a funhouse and everything is teetering from side to side. Everything has taken on a look somewhat like tuss, but more pleasurable, more plastic like. The next movie is The Punisher. Kick-Ass. All the explosions and loud noises make me quite happy. In fact I get really uncomfortable when they are not happening. I feel like the gravity has increased a notch, but I have to go to the bathroom so I attempt going up the stairs. Very difficult. I stumble around the walls and I feel like I am kind of flying but can still see my body stumbling around, a mini out of body experience
This continued on throughout the night (The Punisher was awesome) and allowed me quite a few cool visuals but no hallucinations. Colors looked much more vivid and the body buzz was incredible. I hope to try this again with a higher dose so that I really do trip and see cool things.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


| 1 |
2PCwithBTM |
A modified version of P2TCommit (Gray & Lamport, 2006) |
Murat Demirbas |
|
✔ |
FinSet, Int, Seq |
| 2 |
802.16 |
IEEE 802.16 WiMAX Protocols |
Prasad Narayana, Ruiming Chen, Yao Zhao, Yan Chen, Zhi (Judy) Fu, and Hai Zhou |
|
✔ |
Int, Seq, FinSet |
| 3 |
aba-asyn-byz |
Asynchronous Byzantine agreement (Bracha & Toueg, 1985) |
Thanh Hai Tran, Igor Konnov, Josef Widder |
|
✔ |
Nat |
| 4 |
acp-nb |
Non-blocking atomic commitment with a reliable broadcast (Babaoğlu & Toueg, 1993) |
Stephan Merz |
|
✔ |
default theories |
| 5 |
acp-nb-wrong |
Wrong version of the non-blocking atomic commitment with a reliable broadcast (Babaoğlu & Toueg, 1993) |
Stephan Merz |
|
✔ |
default theories |
| 6 |
acp-sb |
Non-blocking atomic commitment with a simple broadcast (Babaoğlu & Toueg, 1993) |
Stephan Merz |
|
✔ |
default theories |
| 7 |
allocator |
Specification of a resource allocator |
Stephan Merz |
|
✔ |
FinSet |
| 8 |
async-comm |
The diversity of asynchronous communication (Chevrou et al., 2016) |
Florent Chevrou, Aurélie Hurault, Philippe Quéinnec |
|
✔ |
Nat |
| 9 |
bcastByz |
Asynchronous reliable broadcast - Figure 7 (Srikanth & Toeug, 1987) |
Thanh Hai Tran, Igor Konnov, Josef Widder |
✔ |
✔ |
Nat, FinSet |
| 10 |
bcastFolklore |
Folklore reliable broadcast - Figure 4 (Chandra and Toueg, 1996) |
Thanh Hai Tran, Igor Konnov, Josef Widder |
✔ |
✔ |
Nat |
| 11 |
bosco |
One-Step Byzantine asynchronous consensus (Song & Renesse, 2008) |
Thanh Hai Tran, Igor Konnov, Josef Widder |
|
✔ |
Nat, FinSet |
| 12 |
Boulangerie |
A variant of the bakery algorithm (Yoram & Patkin, 2015) |
Stephan Merz |
✔ |
✔ |
Int |
| 13 |
byihive |
Based on RFC3506 - Requirements and Design for Voucher Trading System (Fujimura & Eastlake) |
Santhosh Raju |
|
✔ |
default theories |
| 14 |
byzpaxos |
Byzantizing Paxos by Refinement (Lamport, 2011) |
Leslie Lamport? |
|
✔ |
Int, FinSet |
| 15 |
c1cs |
Consensus in one communication step (Brasileiro et al., 2001) |
Thanh Hai Tran, Igor Konnov, Josef Widder |
|
✔ |
Int, FinSet |
| 16 |
Caesar |
Multi-leader generalized consensus protocol (Arun et al., 2017) |
Giuliano Losa |
|
✔ |
FinSet, Seq, Int |
| 17 |
CarTalkPuzzle |
A TLA+ specification of the solution to a nice puzzle. |
|
|
✔ |
Int |
| 18 |
CASPaxos |
An extension of the single-decree Paxos algorithm to a compare-and-swap type register (Rystsov) |
Tobias Schottdorf |
|
✔ |
Int, FinSet |
| 19 |
cbc_max |
Condition-based consensus (Mostefaoui et al., 2003) |
Thanh Hai Tran, Igor Konnov, Josef Widder |
|
✔ |
Int, FinSet |
| 20 |
cf1s-folklore |
One-step consensus with zero-degradation (Dobre & Suri, 2006) |
Thanh Hai Tran, Igor Konnov, Josef Widder |
|
✔ |
Nat |
| 21 |
ChangRoberts |
Leader election in a ring (Chang & Rosemary, 1979) |
Stephan Merz |
|
✔ |
Nat, Seq |
| 22 |
DataPort |
Dataport protocal 505.89PT, only PDF files (Biggs & Noriaki, 2016) |
Geoffrey Biggs, Noriaki Ando |
|
|
Int, Seq |
| 23 |
detector_chan96 |
Chandra and Toueg’s eventually perfect failure detector |
Thanh Hai Tran, Igor Konnov, Josef Widder |
|
✔ |
Int, FinSet |
| 24 |
DieHard |
A very elementary example based on a puzzle from a movie |
|
|
✔ |
Nat |
| 25 |
dijkstra-mutex |
Mutual exclusion algorithm (Dijkstra, 1965) |
Markus Alexander Kuppe |
|
✔ |
Int |
| 26 |
diskpaxos |
Disk Paxos (Gafni & Lamport, 2003) |
Giuliano Losa |
|
✔ |
Int |
| 27 |
egalitarian-paxos |
Leaderless replication protocol based on Paxos (Moraru et al., 2013) |
Iulian Moraru |
|
✔ |
Nat, FinSet |
| 28 |
ewd840 |
Termination detection in a ring (Dijkstra et al., 1986) |
Stephan Merz |
✔ |
✔ |
Nat |
| 29 |
fastpaxos |
An extension of the classic Paxos algorithm, only PDF files (Lamport, 2006) |
Heidi Howard |
|
|
Nat, FinSet |
| 30 |
fpaxos |
A variant of Paxos with flexible quorums (Howard et al., 2017) |
Heidi Howard |
|
✔ |
Int |
| 31 |
HLC |
Hybrid logical clocks and hybrid vector clocks (Demirbas et al., 2014) |
Murat Demirbas |
|
✔ |
Int |
| 32 |
L1 |
Data center network L1 switch protocol, only PDF files (Thacker) |
Tom Rodeheffer |
|
|
FinSet, Nat, Seq |
| 33 |
lamport_mutex |
Mutual exclusion (Lamport, 1978) |
Stephan Merz |
✔ |
✔ |
Nat, Seq |
| 34 |
leaderless |
Leaderless generalized-consensus algorithms (Losa, 2016) |
Giuliano Losa |
|
✔ |
FinSet, Int, Seq |
| 35 |
losa_ap |
The assignment problem, a variant of the allocation problem (Delporte-Gallet, 2018) |
Giuliano Losa |
|
✔ |
FinSet, Nat, Seq |
| 36 |
losa_rda |
Applying peculative linearizability to fault-tolerant message-passing algorithms and shared-memory consensus, only PDF files (Losa, 2014) |
Giuliano Losa |
|
|
FinSet, Nat, Seq |
| 37 |
m2paxos |
Multi-leader consensus protocols (Peluso et al., 2016) |
Giuliano Losa |
|
✔ |
Int, Seq, FinSet |
| 38 |
mongo-repl-tla |
A simplified part of Raft in MongoDB (Ongaro, 2014) |
Siyuan Zhou |
|
✔ |
FinSet, Nat, Seq |
| 39 |
MultiPaxos |
The abstract specification of Generalized Paxos (Lamport, 2004) |
Giuliano Losa |
|
✔ |
Int, FinSet |
| 40 |
N-Queens |
The N queens problem |
Stephan Merz |
|
✔ |
Nat, Seq |
| 41 |
naiad |
Naiad clock protocol, only PDF files (Murray et al., 2013) |
Tom Rodeheffer |
|
✔ |
Int, Seq, FinSet |
| 42 |
nbacc_ray97 |
Asynchronous non-blocking atomic commit (Raynal, 1997) |
Thanh Hai Tran, Igor Konnov, Josef Widder |
|
✔ |
Nat, FinSet |
| 43 |
nbacg_guer01 |
On the hardness of failure-sensitive agreement problems (Guerraoui, 2001) |
Thanh Hai Tran, Igor Konnov, Josef Widder |
|
✔ |
Nat, FinSet |
| 44 |
nfc04 |
Non-functional properties of component-based software systems (Zschaler, 2010) |
Steffen Zschaler |
|
✔ |
Real, Nat |
| 45 |
Paxos |
Paxos consensus algorithm (Lamport, 1998) |
Leslie Lamport? |
|
✔ |
Int, FinSet |
| 46 |
Prisoners |
A puzzle was presented on an American radio program. |
|
|
✔ |
Nat, FinSet |
| 47 |
raft |
Raft consensus algorithm (Ongaro, 2014) |
Diego Ongaro |
|
✔ |
FinSet, Nat, Seq |
| 48 |
SnapshotIsolation |
Serializable snapshot isolation (Cahill et al., 2010) |
Michael J. Cahill, Uwe Röhm, Alan D. Fekete |
|
✔ |
FinSet, Int, Seq |
| 49 |
spanning |
Spanning tree broadcast algorithm in Attiya and Welch’s book |
Thanh Hai Tran, Igor Konnov, Josef Widder |
|
✔ |
Int |
| 50 |
SpecifyingSystems |
Examples to accompany the book Specifying Systems (Lamport, 2002) |
|
|
✔ |
all modules |
| 51 |
Stones |
The same proble as CarTalkPuzzle |
|
|
✔ |
FinSet, Int, Seq |
| 52 |
sums_even |
Two proofs for showing that x+x is even, for any natural number x. |
|
✔ |
✔ |
Int |
| 53 |
SyncConsensus |
Synchronized round consensus algorithm (Demirbas) |
Murat Demirbas |
|
✔ |
FinSet, Int, Seq |
| 54 |
Termination |
Channel counting algorithm (Mattern, 1987) |
Giuliano Losa |
|
✔ |
FinSet, Bags, Nat |
| 55 |
Tla-tortoise-hare |
Robert Floyd’s cycle detection algorithm |
Lorin Hochstein |
|
✔ |
Nat |
| 56 |
tower_of_hanoi |
The well-known Towers of Hanoi puzzle. |
|
|
✔ |
FinSet, Nat, Bit |
| 57 |
transaction_commit |
Consensus on transaction commit (Gray & Lamport, 2006) |
Vasily Kuznetsov, Markus Alexander Kuppe |
|
✔ |
Int |
| 58 |
TransitiveClosure |
The transitive closure of a relation |
|
|
✔ |
FinSet, Int, Seq |
| 59 |
TwoPhase |
Two-phase handshaking |
Stephan Merz |
|
✔ |
Nat |
| 60 |
VoldemortKV |
Voldemort distributed key value store |
Murat Demirbas |
|
✔ |
FinSet, Int, Seq |


ExoJAX¶
ExoJAX provides an auto-differentiable high-resolution spectrum model for exoplanets/brown dwarfs using JAX.
- Fitting a Voigt Profile
- CO Cross Section using HITRAN
- CO Cross Section using ExoMol
- Comparing HITEMP and ExoMol
- CIA Absorption Coefficient
- Rigid Stellar Rotation and Gaussian Convolution
- Forward Modeling of an Emission Spectrum
- Reverse Modeling of an Emission Spectrum
- 🐱 Bayes Inference of a Real Spectrum of Luhman 16A
- Optimization of a Voigt profile
Collaborations using exojax is welcome!
Reference¶
Kawahara et al. under review.
License & Attribution¶
Copyright 2021 Hajime Kawahara.
ExoJAX is free software made available under the MIT License. For details
see the LICENSE
.


Common problems and their solution¶
The most important parts in PyPDEVS are guarded by a DEVSException. Such an exception being thrown is probably due to a modelling error (or more likely: a bug in the simulator). These exceptions should contain enough information about what went wrong and should normally only be seen if violations of DEVS were written (or a simulator bug).
Other problems are often caused due to an ommission of the modeller. This section tries to provide an overview of common problems for first-time modellers using PyPDEVS.
ImportError: No module named X¶
This indicates that PyPDEVS isn’t imported correctly. Make sure that you have installed PyPDEVS, and all its dependencies, correctly.
AttributeError: ‘X’ object has no attribute ‘IPorts’ (or ‘OPorts’ or ‘componentSet’)¶
This problem indicates that you forgot to initialize the superclass of your own DEVS models as the first instruction. For example:
class MyAtomicDEVSModel(AtomicDEVS):
def __init__(self):
AtomicDEVS.__init__(self, 'name') # <-- you probably forgot this line
# Remainder of your initialisation
The same should happen for CoupledDEVS models:
class MyCoupledDEVSModel(CoupledDEVS):
def __init__(self):
CoupledDEVS.__init__(self, 'name') # <-- you probably forgot this line
# Remainder of your initialisation
TypeError: ‘NoneType’ object is not iterable¶
This most likely indicates that you forgot to return a dictionary in the outputFnc function. Even if no output is generated, it is mandatory to return a dictionary:
def outputFnc(self):
return {} # <-- This is required
TypeError: ‘X’ object is not iterable¶
Note
This solution is not valid in Classic DEVS simulation, as here it is allowed to be a simple value.
Probably, you forgot to return the values in your dicationary as a list, as is required in parallel DEVS. For example:
def outputFnc(self):
# return {self.outport: myMessage} <-- WRONG
return {self.outport: [myMessage]}
AttributeError: ‘List’ object has no attribute ‘X’¶
Note
This solution is not valid in Classic DEVS simulation, as here it is allowed to be a simple value.
This is equivalent to the previous error: the values of the inputs dictionary are lists instead of the actual values:
def extTransition(self, inputs):
# processMessage(inputs[self.inport]) <-- WRONG
for msg in inputs[self.inport]:
processMessage(msg)
Warning
To be complete, it is not sufficient to just take the first element from the list, as there might be more elements. Always using [0] carelessly is therefore discouraged.
AttributeError: ‘NoneType’ has no attribute ‘X’¶
You probably forgot to return the new state in one of the transition functions. Transition functions should always return the new state. In case only state attributes are updated, it is necessary to return the self.state variable:
def intTransition(self):
self.state.message = 5 # <-- OK, state is updated
return self.state # <-- Don't forget this
Alternatively:
def intTransition(self):
return State(5) # <-- Simply create a completely new state
New state: <X object at 0xXXXXXXX>¶
Not actually a problem, though it is worth noting that you can have custom string output by defining a __str__(self) function for your state in case it is a class.
AttributeError: ‘module’ object has no attribute ‘YourCoupledDEVSClass’¶
This means that you have a wrong import order. Due to the way MPI runs, it starts up the same file multiple times. To get around this problem, PyPDEVS will stop execution at the server nodes as soon as they are started up. However, they still need to have the actual model to be simulated loaded. For this reason, the import of the simulator file should happend after the import of the models. In case you have your model and experiment in the same file, you should add the import to simulator right before creating the model, preferably even in a conditional:
class MyCoupledDEVSModel(CoupledDEVS):
def __init__(self):
...
if __name__ == "__main__":
from simulator import Simulator
model = MyCoupledDEVSModel()
sim = Simulator(model)
sim.simulate()
The execution of the file will stop as soon as the simulator file is imported, so make sure that all your models are imported by that time. The simplest way to solve this problem is by creating seperate model and experiment files.


THE ABYSS [Spoilers] A film review by Jeff Meyer Copyright 1989 Jeff Meyer
THE ABYSS is an interesting flick, and pretty entertaining; it's also an interesting "case study," in that the entertainment comes much more from the surroundings than the plot. The story works well enough -- nothing special, buoyed mostly by earnest if non-glowing performances by most of the cast; it seems mired in molasses at times, or maybe liquid oxygen. The audience can breath it, but they do it in gulps -- it doesn't flow well.
What *does* leave you with an impression -- and, after time, communicates more emotion than cast or dialogue, really -- is the setting and the way the film was shot. THE ABYSS takes place underwater, WAY underwater, and everything about the film gives that impression; the technical details may be off, but it *feels* right. Cameron has, without a doubt, shot about the best underwater adventure film I can think of. It gives (when seen on a big screen, preferably 70mm -- this film is *not* going to translate into video well, folks) a wonderful sense of claustrophobia, of being under *all* *that* *water*... And the deep dive ascents -- whew! You stop thinking about what they're doing, and just goggle at the spectacle of it all. I think the idea to really shoot this underwater was a good one -- it adds to Suspension of Belief factor immeasurably. (I am curious how much of the underwater vehicle scenes were done with blue-screen effects, though -- perfect place for them.)
Other good points: liked the relationship between Harris and Mastrantonio, though it never really flamed, and was a touch too earnest. And the early "unknown entity" bits were able to get me excited, mainly due to Mastrantonio's acting. Ed Harris shows that 1950s movie heroes can still muddle along in the 1990s. (Though I got this feeling, right towards the end, that he was going to say "Ready to go -- 100%!" in the best John Glenn tones.) Finally, I guess there's still some New Race Contact fascination left in me that wasn't totally sucked out by CLOSE ENCOUNTERS, but the climax seems really visually derivative at points -- kept expecting Richard Dreyfuss to help Harris off with his helmet. ("Hi! Got any Cheetos?")
Still, it's a decent yarn, at least by summer standards; the look of the film is not to be missed, though. Find a 70mm theater this weekend and jump in.
Moriarty, aka Jeff Meyer INTERNET<EMAIL_ADDRESS>Manual UUCP: {uw-beaver, sun, hplsla, thebes, microsoft}!fluke!moriarty
.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


vignettes/troubleshooting.Rmd
troubleshooting.Rmd
This guide covers known issues and troubleshooting for using R in Azure Machine Learning.
The list will continue to evolve as new issues are discovered and old ones are resolved.
For issues with installing the azuremlsdk package, please refer to the troubleshooting section of the installation guide.
The following address issues when developing in R on a Compute instance using RStudio or Jupyter.
There will sometimes be a lag in between the latest release of the azuremlsdk package to CRAN and when the package version is updated on the compute instance. You can determine what version of the SDK you have by running packageVersion("azuremlsdk")
.
To update to the latest version on CRAN:
To install the latest development version from GitHub:
You may run into an error installing R packages from Jupyter using the R kernel, even though the same installation works from RStudio. The error will look as follows:
Installing package into '/usr/local/lib/R/site-library' (as 'lib' is unspecified)
Warning message in install.packages(<package name>):
"'lib = "/usr/local/lib/R/site-library"' is not writable"
The discrepancy is due to RStudio assuming a different default library location than the R kernel in Jupyter.
You can work around this by specifying a library location you have permission to such as the home directory “/home/azureuser/R”.
install.packages("<package name>", lib="/home/azureuser")
.libPaths()
at the beginning of your notebook to tell Jupyter where your packages are:.libPaths("/home/azureuser/R")
An alternative is to give yourself access to the default folder by running a chmod
or chown
command from the terminal.
If the following error occurs for your training run (or deployment):
"ModuleNotFoundError": "No module named 'ruamel'"
This is due to an issue with the installation ruamel.yaml
package required by azureml-defaults
that happens with pip > 20.1.1
.
To work around this issue, you can pin pip
to version 20.1.1. Two options for doing so:
pip=20.1.1
. You can refer to the "Building custom Docker images vignette for an example and more information.If the following error occurs when submitting an experiment using RStudio:
Error in py_call_impl(callable, dots$args, dots$keywords) :
PermissionError: [Errno 13] Permission denied
Move the files for your project into a subdirectory and reset the working directory to that directory before re-submitting.
In order to submit an experiment, the Azure ML SDK must create a .zip file of the project directory to send to the service. However, the SDK does not have permission to write into the .Rproj.user subdirectory that is automatically created during an RStudio session. For this reason, the recommended best practice is to isolate project files into their own directory.
For information on troubleshooting web service deployment issues, see the “Troubleshooting section” of the Deploying models guide.
You may hit resource quota issues, such as the error below:
Operation could not be completed as it results in exceeding approved Total Regional Cores quota.
For information on quotas, see Manage and request quotas for Azure resources.


Thank you for your desire to help Christians in need through the ministry of FARMS International, Inc. You will receive a tax deductible receipt for your donation. FARMS International, Inc. complies fully with federal and state charitable solicitation requirements and is a Member of the Evangelical Council for Financial Accountability.
Your personal information is encrypted and transmitted without risk using a Secure Sockets Layer (SSL) protocol.
"As we have therefore opportunity, let us do good unto all men"