Not working as expected

Sorry, for the not very specific issue title but just nothing works as expected:
var xml = '<?xml version="1.0" encoding="UTF-8"?> \
  <urlset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9  http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd" xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> \
<url> \
  <loc>http://google.com</loc> \
  <lastmod>2010-02-01T02:18:34+00:00</lastmod> \
  <changefreq>daily</changefreq> \
  <priority>1.0</priority> \
</url> \
</urlset>';

var libxmljs = require("libxmljs");
var doc = libxmljs.parseXmlString(xml);
console.log('doc:', doc);
var locations = doc.find('//default:loc', { default: 'http://www.sitemaps.org/schemas/sitemap/0.9' });
console.log('locations:', locations);
for(var i in locations) {
  console.log('l:', locations[i]);
}

resulting in:
doc: { errors: [] }
locations: [ {} ]
l: {}

The output does not make sense on so many levels.
doc should show more information on the document.
locations should show the one child found.
l should show the child.
...but this does not seem to work at all.

I agree it's confusing. We're open to better object representations. Patches are welcome. But we're not sure when we'll get to this.


AudioPreparedListener

I #2 I've added the listener for the AudioPrepared event. I think it is useful.  But don't see it in 0.4 release. That is okay? :)

It's already there. But I've slightly changed interface.


Something wrong when import from csv

Describe the bug
When a file in CSV format is split using tabs, if there are null values, the data cannot be imported.
Error in console：
Uncaught TypeError: Cannot read properties of undefined (reading 'trim')
    at eval (plugin:notion-like-tables:63211:48)
    at Array.forEach (<anonymous>)
    at eval (plugin:notion-like-tables:63202:17)
    at Array.map (<anonymous>)
    at addImportData (plugin:notion-like-tables:63198:55)
    at handleFinishClick (plugin:notion-like-tables:63724:22)
    at handleNextClick (plugin:notion-like-tables:62075:7)
    at handleClick (plugin:notion-like-tables:54356:32)

Steps to reproduce
import test.csv，the data cannot be imported.
test.csv
Expected behavior
The data from the csv file is expected to be loaded as table.
Are you using the mobile app?
Yes
Obsidian debug info
SYSTEM INFO:
Obsidian version: v1.4.16
Installer version: v1.4.13
Operating system: Darwin Kernel Version 23.2.0: Wed Nov 15 21:54:10 PST 2023; root:xnu-10002.61.3~2/RELEASE_X86_64 23.2.0
Login status: logged in
Catalyst license: none
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 2
Plugins enabled: 1
1: DataLoom v8.15.8
Relevant log output
No response

Fixed in 8.5.9


mrxs file format

Thought its better to create a new issue instead of using the other one for mrxs file format
https://github.com/AICAN-Research/FAST-Pathology/issues/6#issuecomment-1007166721

AFAIK MRXS is supported by OpenSlide (see here).
But I realized that I had forgotten to add this as an option in the selectFile method. I therefore made a commit that adds support for MRXS just now: d810332
To use the most recent version of FP (nightly, which has not yet been released). You can download the produced artifact: https://github.com/AICAN-Research/FAST-Pathology/actions/runs/1666348776
Simply download the file "Windows package", unzip, and run the installer to update your FP version.

I can open a mrxs file in FP now, but the file opens like this:

When I run predictions using the Epithelium models in NoCodeSeg, it takes a while and the end result looks like this on an inset:

However, when I export the mrxs file to a tiled-tiff using the CaseViewer software, followed by conversion in vips to a pyramidal tiff (jpeg, quality = 85), and then run predictions, I get this:

The image magnification is 10 for both.
I could share the dataset with you but will have to be via email.
We wouldn't need any agreements. Its just that I can't share it directly as its a cross-institutional project.
The owner will have to share it with you directly.
Cheers
Pradeep

First, regarding the strange zero-padded regions. I think that is actually part of the original image. Could you open it in QuPath and verify that you get the same?
The reason why it might be especially slow, is because the zero-padded regions are assumed to be tissue, as glass is filtered depending on how far away it is from the color white. I could add an option to include uint 0 in the glass class to be filtered.
Also, you opened both these in FP, right? The same WSI in the MXRS and TIFF format, right? Could you send me the prompts for both? Include all. I don't care about inference, just what is displayed when opening the WSI.

Also, you opened both these in FP, right? The same WSI in the MRXS and TIFF format, right? Could you send me the prompts for both? Include all. I don't care about inference, just what is displayed when opening the WSI.

Yes, I opened them both in FP
Yes, same WSI in MRXS and TIFF.
Log for MRXS:
 Dropped file:D:/Colon_sections/andre_mrxs/slide_export/slide_export.mrxs
Selected file: D:/Colon_sections/andre_mrxs/slide_export/slide_export.mrxs
INFO [6568] EXECUTING WholeSlideImageImporter because PO is modified.
INFO [6568] Metadata: mirax.DATAFILE.FILE_0 = Data0000.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_1 = Data0001.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_10 = Data0010.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_11 = Data0011.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_12 = Data0012.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_13 = Data0013.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_14 = Data0014.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_15 = Data0015.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_16 = Data0016.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_17 = Data0017.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_18 = Data0018.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_19 = Data0019.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_2 = Data0002.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_20 = Data0020.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_21 = Data0021.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_22 = Data0022.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_23 = Data0023.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_24 = Data0024.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_25 = Data0025.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_26 = Data0026.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_27 = Data0027.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_28 = Data0028.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_29 = Data0029.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_3 = Data0003.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_30 = Data0030.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_31 = Data0031.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_32 = Data0032.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_33 = Data0033.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_4 = Data0004.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_5 = Data0005.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_6 = Data0006.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_7 = Data0007.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_8 = Data0008.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_9 = Data0009.dat
INFO [6568] Metadata: mirax.DATAFILE.FILE_COUNT = 34
INFO [6568] Metadata: mirax.GENERAL.ADAPTER_SIZE = 1
INFO [6568] Metadata: mirax.GENERAL.CAMERA_TYPE = Point Grey GS3-U3-51S5M-C
INFO [6568] Metadata: mirax.GENERAL.COMPRESSED = True
INFO [6568] Metadata: mirax.GENERAL.COMPRESSION = JPEG
INFO [6568] Metadata: mirax.GENERAL.COMPRESSION_FACTOR = 60
INFO [6568] Metadata: mirax.GENERAL.CONFOCAL = NO
INFO [6568] Metadata: mirax.GENERAL.CURRENT_SLIDE_VERSION = 2.3
INFO [6568] Metadata: mirax.GENERAL.CameraImageDivisionsPerSide = 1
INFO [6568] Metadata: mirax.GENERAL.DISK_POSITION = 0
INFO [6568] Metadata: mirax.GENERAL.EXTENDED_FOCUS_ALGORITHM = FL Image
INFO [6568] Metadata: mirax.GENERAL.FLAT_FIELD_CORRECTION = DISABLED
INFO [6568] Metadata: mirax.GENERAL.FOCUS_LIMIT = DISABLED
INFO [6568] Metadata: mirax.GENERAL.FOCUS_MAP = AUTO
INFO [6568] Metadata: mirax.GENERAL.IMAGENUMBER_X = 344
INFO [6568] Metadata: mirax.GENERAL.IMAGENUMBER_Y = 813
INFO [6568] Metadata: mirax.GENERAL.IMAGE_OVERLAP_MICROMETERS_X = 0
INFO [6568] Metadata: mirax.GENERAL.IMAGE_OVERLAP_MICROMETERS_Y = 0
INFO [6568] Metadata: mirax.GENERAL.OBJECTIVE_MAGNIFICATION = 20
INFO [6568] Metadata: mirax.GENERAL.OBJECTIVE_NAME = Plan-Apochromat
INFO [6568] Metadata: mirax.GENERAL.OPTOVAR_SIZE = 1
INFO [6568] Metadata: mirax.GENERAL.PROJECT_NAME = Default
INFO [6568] Metadata: mirax.GENERAL.SLIDE_CONTENT = DIGITAL_SLIDE
INFO [6568] Metadata: mirax.GENERAL.SLIDE_CREATIONDATETIME = 26/11/2021 15:56:12
INFO [6568] Metadata: mirax.GENERAL.SLIDE_CREATION_FINISHED = True
INFO [6568] Metadata: mirax.GENERAL.SLIDE_ID = 35AC89AE57A14B66BF3A12AA022F839D
INFO [6568] Metadata: mirax.GENERAL.SLIDE_NAME = slide_export
INFO [6568] Metadata: mirax.GENERAL.SLIDE_POSITION_X = 0
INFO [6568] Metadata: mirax.GENERAL.SLIDE_POSITION_Y = 0
INFO [6568] Metadata: mirax.GENERAL.SLIDE_TYPE = SLIDE_TYPE_BRIGHTFIELD
INFO [6568] Metadata: mirax.GENERAL.SLIDE_VERSION = 01.03
INFO [6568] Metadata: mirax.GENERAL.VIMSLIDE_CAMERA_REAL_BITDEPTH = 24
INFO [6568] Metadata: mirax.GENERAL.VIMSLIDE_SLIDE_BITDEPTH = 8
INFO [6568] Metadata: mirax.GENERAL.VIMSLIDE_SLIDE_ROTATION = 360
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_COUNT = 10
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_DEFAULT = 0
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_NAME = Slide zoom level
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_SECTION = LAYER_0_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_0 = ZoomLevel_0
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_0_SECTION = LAYER_0_LEVEL_0_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_1 = ZoomLevel_1
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_1_SECTION = LAYER_0_LEVEL_1_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_2 = ZoomLevel_2
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_2_SECTION = LAYER_0_LEVEL_2_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_3 = ZoomLevel_3
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_3_SECTION = LAYER_0_LEVEL_3_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_4 = ZoomLevel_4
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_4_SECTION = LAYER_0_LEVEL_4_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_5 = ZoomLevel_5
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_5_SECTION = LAYER_0_LEVEL_5_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_6 = ZoomLevel_6
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_6_SECTION = LAYER_0_LEVEL_6_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_7 = ZoomLevel_7
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_7_SECTION = LAYER_0_LEVEL_7_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_8 = ZoomLevel_8
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_8_SECTION = LAYER_0_LEVEL_8_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_9 = ZoomLevel_9
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_0_VAL_9_SECTION = LAYER_0_LEVEL_9_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_1_COUNT = 2
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_1_DEFAULT = 0
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_1_NAME = Slide zoom mask level2
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_1_SECTION = LAYER_1_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_1_VAL_0 = ZoomMaskDefault
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_1_VAL_0_SECTION = LAYER_1_LEVEL_0_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_1_VAL_1 = ZoomMaskData
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_1_VAL_1_SECTION = LAYER_1_LEVEL_1_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_2_COUNT = 3
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_2_DEFAULT = 0
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_2_NAME = Slide filter level
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_2_SECTION = LAYER_2_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_2_VAL_0 = FilterLevel_0
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_2_VAL_0_SECTION = LAYER_2_LEVEL_0_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_2_VAL_1 = FilterLevel_1
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_2_VAL_1_SECTION = LAYER_2_LEVEL_1_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_2_VAL_2 = FilterLevel_2
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_2_VAL_2_SECTION = LAYER_2_LEVEL_2_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_3_COUNT = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_3_DEFAULT = 0
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_3_NAME = Microscope focus level
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_3_SECTION = LAYER_3_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_3_VAL_0 = ExtFocusLevel
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_3_VAL_0_SECTION = LAYER_3_LEVEL_0_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.HIER_COUNT = 4
INFO [6568] Metadata: mirax.HIERARCHICAL.INDEXFILE = Index.dat
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_0_COUNT = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_0_NAME = StitchingLayerForHWCoord
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_0_SECTION = NONHIERLAYER_0_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_0_VAL_0 = StitchingLevelForHWCoord
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_0_VAL_0_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_0_VAL_0_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_0_VAL_0_SECTION = NONHIERLAYER_0_LEVEL_0_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_COUNT = 10
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_NAME = Scan data layer
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_SECTION = NONHIERLAYER_1_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_0 = ScanDataLayer_ScanMap
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_0_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_0_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_0_SECTION = NONHIERLAYER_1_LEVEL_0_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_1 = ScanDataLayer_XMLInfoHeader
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_1_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_1_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_1_SECTION = NONHIERLAYER_1_LEVEL_1_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_2 = ScanDataLayer_SlideThumbnail
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_2_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_2_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_2_SECTION = NONHIERLAYER_1_LEVEL_2_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_3 = ScanDataLayer_SlideBarcode
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_3_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_3_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_3_SECTION = NONHIERLAYER_1_LEVEL_3_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_4 = ScanDataLayer_SlidePreview
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_4_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_4_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_4_SECTION = NONHIERLAYER_1_LEVEL_4_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_5 = ScanDataLayer_StagePositionMap
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_5_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_5_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_5_SECTION = NONHIERLAYER_1_LEVEL_5_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_6 = ScanDataLayer_Empty
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_6_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_6_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_6_SECTION = NONHIERLAYER_1_LEVEL_6_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_7 = ProfileXMLHeader
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_7_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_7_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_7_SECTION = NONHIERLAYER_1_LEVEL_7_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_8 = ProfileXML
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_8_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_8_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_8_SECTION = NONHIERLAYER_1_LEVEL_8_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_9 = ScannedFOVsMap
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_9_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_9_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_1_VAL_9_SECTION = NONHIERLAYER_1_LEVEL_9_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_2_COUNT = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_2_NAME = StitchingLayer
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_2_SECTION = NONHIERLAYER_2_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_2_VAL_0 = DataLevel_V1.0
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_2_VAL_0_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_2_VAL_0_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_2_VAL_0_SECTION = NONHIERLAYER_2_LEVEL_0_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_3_COUNT = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_3_NAME = VIMSLIDE_HISTOGRAM_DATA
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_3_SECTION = NONHIERLAYER_3_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_3_VAL_0 = default
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_3_VAL_0_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_3_VAL_0_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_3_VAL_0_SECTION = NONHIERLAYER_3_LEVEL_0_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_4_COUNT = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_4_NAME = Slide object layer
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_4_SECTION = NONHIERLAYER_4_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_4_VAL_0 = SlideObjectLayer_SlideFlag
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_4_VAL_0_IMAGENUMBER_X = 5
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_4_VAL_0_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_4_VAL_0_SECTION = NONHIERLAYER_4_LEVEL_0_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_5_COUNT = 2
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_5_NAME = ScanInfoLayer
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_5_SECTION = NONHIERLAYER_5_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_5_VAL_0 = ScanInfoHeaderLevel
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_5_VAL_0_IMAGENUMBER_X = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_5_VAL_0_IMAGENUMBER_Y = 1
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_5_VAL_0_SECTION = NONHIERLAYER_5_LEVEL_0_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_5_VAL_1 = ScanInfoDataLevel
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_5_VAL_1_IMAGENUMBER_X = 2
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_5_VAL_1_IMAGENUMBER_Y = 5
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_5_VAL_1_SECTION = NONHIERLAYER_5_LEVEL_1_SECTION
INFO [6568] Metadata: mirax.HIERARCHICAL.NONHIER_COUNT = 6
INFO [6568] Metadata: mirax.HIERARCHICAL.PAGEELEMENTCOUNT = 128
INFO [6568] Metadata: mirax.HIERARCHICAL.PAGELENGTH = 2048
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_0_SECTION.DIGITIZER_HEIGHT = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_0_SECTION.DIGITIZER_WIDTH = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_0_SECTION.IMAGE_COMPRESSION_FACTOR = 60
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_0_SECTION.IMAGE_CONCAT_FACTOR = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_0_SECTION.IMAGE_FILL_COLOR_BGR = 16777215
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_0_SECTION.IMAGE_FORMAT = JPEG
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_0_SECTION.MICROMETER_PER_PIXEL_X = 0.249710957804617
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_0_SECTION.MICROMETER_PER_PIXEL_Y = 0.249968497983871
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_0_SECTION.OVERLAP_X = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_0_SECTION.OVERLAP_Y = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_1_SECTION.DIGITIZER_HEIGHT = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_1_SECTION.DIGITIZER_WIDTH = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_1_SECTION.IMAGE_COMPRESSION_FACTOR = 60
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_1_SECTION.IMAGE_CONCAT_FACTOR = 1
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_1_SECTION.IMAGE_FILL_COLOR_BGR = 16777215
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_1_SECTION.IMAGE_FORMAT = JPEG
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_1_SECTION.MICROMETER_PER_PIXEL_X = 0.499421915609234
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_1_SECTION.MICROMETER_PER_PIXEL_Y = 0.499936995967742
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_1_SECTION.OVERLAP_X = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_1_SECTION.OVERLAP_Y = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_2_SECTION.DIGITIZER_HEIGHT = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_2_SECTION.DIGITIZER_WIDTH = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_2_SECTION.IMAGE_COMPRESSION_FACTOR = 60
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_2_SECTION.IMAGE_CONCAT_FACTOR = 1
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_2_SECTION.IMAGE_FILL_COLOR_BGR = 16777215
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_2_SECTION.IMAGE_FORMAT = JPEG
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_2_SECTION.MICROMETER_PER_PIXEL_X = 0.998843831218468
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_2_SECTION.MICROMETER_PER_PIXEL_Y = 0.999873991935484
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_2_SECTION.OVERLAP_X = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_2_SECTION.OVERLAP_Y = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_3_SECTION.DIGITIZER_HEIGHT = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_3_SECTION.DIGITIZER_WIDTH = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_3_SECTION.IMAGE_COMPRESSION_FACTOR = 60
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_3_SECTION.IMAGE_CONCAT_FACTOR = 1
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_3_SECTION.IMAGE_FILL_COLOR_BGR = 16777215
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_3_SECTION.IMAGE_FORMAT = JPEG
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_3_SECTION.MICROMETER_PER_PIXEL_X = 1.99768766243694
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_3_SECTION.MICROMETER_PER_PIXEL_Y = 1.99974798387097
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_3_SECTION.OVERLAP_X = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_3_SECTION.OVERLAP_Y = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_4_SECTION.DIGITIZER_HEIGHT = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_4_SECTION.DIGITIZER_WIDTH = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_4_SECTION.IMAGE_COMPRESSION_FACTOR = 60
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_4_SECTION.IMAGE_CONCAT_FACTOR = 1
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_4_SECTION.IMAGE_FILL_COLOR_BGR = 16777215
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_4_SECTION.IMAGE_FORMAT = JPEG
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_4_SECTION.MICROMETER_PER_PIXEL_X = 3.99537532487387
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_4_SECTION.MICROMETER_PER_PIXEL_Y = 3.99949596774194
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_4_SECTION.OVERLAP_X = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_4_SECTION.OVERLAP_Y = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_5_SECTION.DIGITIZER_HEIGHT = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_5_SECTION.DIGITIZER_WIDTH = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_5_SECTION.IMAGE_COMPRESSION_FACTOR = 60
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_5_SECTION.IMAGE_CONCAT_FACTOR = 1
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_5_SECTION.IMAGE_FILL_COLOR_BGR = 16777215
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_5_SECTION.IMAGE_FORMAT = JPEG
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_5_SECTION.MICROMETER_PER_PIXEL_X = 7.99075064974774
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_5_SECTION.MICROMETER_PER_PIXEL_Y = 7.99899193548387
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_5_SECTION.OVERLAP_X = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_5_SECTION.OVERLAP_Y = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_6_SECTION.DIGITIZER_HEIGHT = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_6_SECTION.DIGITIZER_WIDTH = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_6_SECTION.IMAGE_COMPRESSION_FACTOR = 60
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_6_SECTION.IMAGE_CONCAT_FACTOR = 1
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_6_SECTION.IMAGE_FILL_COLOR_BGR = 16777215
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_6_SECTION.IMAGE_FORMAT = JPEG
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_6_SECTION.MICROMETER_PER_PIXEL_X = 15.9815012994955
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_6_SECTION.MICROMETER_PER_PIXEL_Y = 15.9979838709677
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_6_SECTION.OVERLAP_X = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_6_SECTION.OVERLAP_Y = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_7_SECTION.DIGITIZER_HEIGHT = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_7_SECTION.DIGITIZER_WIDTH = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_7_SECTION.IMAGE_COMPRESSION_FACTOR = 60
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_7_SECTION.IMAGE_CONCAT_FACTOR = 1
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_7_SECTION.IMAGE_FILL_COLOR_BGR = 16777215
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_7_SECTION.IMAGE_FORMAT = JPEG
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_7_SECTION.MICROMETER_PER_PIXEL_X = 31.963002598991
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_7_SECTION.MICROMETER_PER_PIXEL_Y = 31.9959677419355
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_7_SECTION.OVERLAP_X = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_7_SECTION.OVERLAP_Y = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_8_SECTION.DIGITIZER_HEIGHT = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_8_SECTION.DIGITIZER_WIDTH = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_8_SECTION.IMAGE_COMPRESSION_FACTOR = 60
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_8_SECTION.IMAGE_CONCAT_FACTOR = 1
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_8_SECTION.IMAGE_FILL_COLOR_BGR = 16777215
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_8_SECTION.IMAGE_FORMAT = JPEG
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_8_SECTION.MICROMETER_PER_PIXEL_X = 63.926005197982
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_8_SECTION.MICROMETER_PER_PIXEL_Y = 63.991935483871
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_8_SECTION.OVERLAP_X = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_8_SECTION.OVERLAP_Y = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_9_SECTION.DIGITIZER_HEIGHT = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_9_SECTION.DIGITIZER_WIDTH = 256
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_9_SECTION.IMAGE_COMPRESSION_FACTOR = 60
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_9_SECTION.IMAGE_CONCAT_FACTOR = 1
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_9_SECTION.IMAGE_FILL_COLOR_BGR = 16777215
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_9_SECTION.IMAGE_FORMAT = JPEG
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_9_SECTION.MICROMETER_PER_PIXEL_X =<PHONE_NUMBER>95964
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_9_SECTION.MICROMETER_PER_PIXEL_Y =<PHONE_NUMBER>67742
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_9_SECTION.OVERLAP_X = 0
INFO [6568] Metadata: mirax.LAYER_0_LEVEL_9_SECTION.OVERLAP_Y = 0
INFO [6568] Metadata: mirax.LAYER_0_SECTION.SHARPENED = 16
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.ACTIVE = ON
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.COLOR_B = 255
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.COLOR_G = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.COLOR_R = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.DATA_IN_THIS_FILTER_LEVEL = FilterLevel_0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.DIGITALGAIN = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.EMISSION_BANDWIDTH = 60
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.EMISSION_WAVELENGTH = 447
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.EXCITATION_BANDWIDTH = 50
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.EXCITATION_WAVELENGTH = 377
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.EXPOSUREPERCENTAGE = 100
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.EXTENDED_STEP_COUNT = 1
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.EXTENDED_STEP_SIZE = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.FILTER_NAME = Default
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.FILTER_REAL_POSITION = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.IS_MASTER_FILTER = False
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.IS_STITCHING_FILTER = 1
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.MODIFIED_COLOR_B = 255
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.MODIFIED_COLOR_G = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.MODIFIED_COLOR_R = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.MODIFY = ON
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.STORING_CHANNEL_NUMBER = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.THRESHOLD = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.USE_BLUE_CHANNEL = False
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.USE_GREEN_CHANNEL = False
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.USE_RED_CHANNEL = True
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.VIMSLIDE_HISTOGRAM_DATA_CHANNEL_SIZE = 256
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.XDIFF = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.YDIFF = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.ZDIFF = 2.32
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.ZSTACK_FIRST_LEVEL = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_0_SECTION.ZSTACK_STEP_COUNT = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.ACTIVE = ON
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.COLOR_B = 255
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.COLOR_G = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.COLOR_R = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.DATA_IN_THIS_FILTER_LEVEL = FilterLevel_0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.DIGITALGAIN = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.EMISSION_BANDWIDTH = 60
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.EMISSION_WAVELENGTH = 447
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.EXCITATION_BANDWIDTH = 50
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.EXCITATION_WAVELENGTH = 377
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.EXPOSUREPERCENTAGE = 100
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.EXTENDED_STEP_COUNT = 1
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.EXTENDED_STEP_SIZE = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.FILTER_NAME = Default
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.FILTER_REAL_POSITION = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.IS_MASTER_FILTER = False
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.IS_STITCHING_FILTER = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.MODIFIED_COLOR_B = 255
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.MODIFIED_COLOR_G = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.MODIFIED_COLOR_R = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.MODIFY = ON
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.STORING_CHANNEL_NUMBER = 1
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.THRESHOLD = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.USE_BLUE_CHANNEL = False
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.USE_GREEN_CHANNEL = False
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.USE_RED_CHANNEL = True
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.VIMSLIDE_HISTOGRAM_DATA_CHANNEL_SIZE = 256
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.XDIFF = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.YDIFF = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.ZDIFF = 2.32
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.ZSTACK_FIRST_LEVEL = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_1_SECTION.ZSTACK_STEP_COUNT = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.ACTIVE = ON
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.COLOR_B = 255
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.COLOR_G = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.COLOR_R = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.DATA_IN_THIS_FILTER_LEVEL = FilterLevel_0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.DIGITALGAIN = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.EMISSION_BANDWIDTH = 60
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.EMISSION_WAVELENGTH = 447
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.EXCITATION_BANDWIDTH = 50
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.EXCITATION_WAVELENGTH = 377
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.EXPOSUREPERCENTAGE = 100
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.EXTENDED_STEP_COUNT = 1
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.EXTENDED_STEP_SIZE = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.FILTER_NAME = Default
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.FILTER_REAL_POSITION = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.IS_MASTER_FILTER = True
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.IS_STITCHING_FILTER = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.MODIFIED_COLOR_B = 255
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.MODIFIED_COLOR_G = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.MODIFIED_COLOR_R = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.MODIFY = ON
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.STORING_CHANNEL_NUMBER = 2
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.THRESHOLD = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.USE_BLUE_CHANNEL = False
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.USE_GREEN_CHANNEL = False
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.USE_RED_CHANNEL = True
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.VIMSLIDE_HISTOGRAM_DATA_CHANNEL_SIZE = 256
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.XDIFF = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.YDIFF = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.ZDIFF = 2.32
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.ZSTACK_FIRST_LEVEL = 0
INFO [6568] Metadata: mirax.LAYER_2_LEVEL_2_SECTION.ZSTACK_STEP_COUNT = 0
INFO [6568] Metadata: mirax.LAYER_3_LEVEL_0_SECTION.OFFSET_IN_MICROMETERS = 0
INFO [6568] Metadata: mirax.LAYER_3_SECTION.EXTENDED_FOCUS_LEVEL = -1
INFO [6568] Metadata: mirax.LAYER_3_SECTION.LAST_Z_STACKED_ZOOM_LEVEL = 10
INFO [6568] Metadata: mirax.LAYER_3_SECTION.ZERO_FOCUS_LEVEL = 0
INFO [6568] Metadata: mirax.NONHIERLAYER_0_LEVEL_0_SECTION.COMPRESSED_STITCHING_ORIG_CAMERA_TILE_OVERLAP_X = 120
INFO [6568] Metadata: mirax.NONHIERLAYER_0_LEVEL_0_SECTION.COMPRESSED_STITCHING_ORIG_CAMERA_TILE_OVERLAP_Y = 120
INFO [6568] Metadata: mirax.NONHIERLAYER_0_LEVEL_0_SECTION.COMPRESSED_STITCHING_ORIG_SLIDE_SCANNED_AREA_IN_PIXELS__BOTTOM = 208119
INFO [6568] Metadata: mirax.NONHIERLAYER_0_LEVEL_0_SECTION.COMPRESSED_STITCHING_ORIG_SLIDE_SCANNED_AREA_IN_PIXELS__LEFT = 1608
INFO [6568] Metadata: mirax.NONHIERLAYER_0_LEVEL_0_SECTION.COMPRESSED_STITCHING_ORIG_SLIDE_SCANNED_AREA_IN_PIXELS__RIGHT = 87895
INFO [6568] Metadata: mirax.NONHIERLAYER_0_LEVEL_0_SECTION.COMPRESSED_STITCHING_ORIG_SLIDE_SCANNED_AREA_IN_PIXELS__TOP = 9306
INFO [6568] Metadata: mirax.NONHIERLAYER_0_LEVEL_0_SECTION.COMPRESSSED_STITCHING_ORIG_CAMERA_TILE_HEIGHT = 2024
INFO [6568] Metadata: mirax.NONHIERLAYER_0_LEVEL_0_SECTION.COMPRESSSED_STITCHING_ORIG_CAMERA_TILE_WIDTH = 2424
INFO [6568] Metadata: mirax.NONHIERLAYER_0_LEVEL_0_SECTION.COMPRESSSED_STITCHING_TABLE_HEIGHT = 156
INFO [6568] Metadata: mirax.NONHIERLAYER_0_LEVEL_0_SECTION.COMPRESSSED_STITCHING_TABLE_WIDTH = 54
INFO [6568] Metadata: mirax.NONHIERLAYER_0_LEVEL_0_SECTION.COMPRESSSED_STITCHING_VERSION = 1
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_0_SECTION.SCANMAP_IMAGE_HEIGHT = 156
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_0_SECTION.SCANMAP_IMAGE_TYPE = PNG
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_0_SECTION.SCANMAP_IMAGE_WIDTH = 54
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_2_SECTION.THUMBNAIL_IMAGE_HEIGHT = 3414
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_2_SECTION.THUMBNAIL_IMAGE_TYPE = JPEG
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_2_SECTION.THUMBNAIL_IMAGE_WIDTH = 1448
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_3_SECTION.BARCODE_IMAGE_HEIGHT = 1221
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_3_SECTION.BARCODE_IMAGE_TYPE = JPEG
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_3_SECTION.BARCODE_IMAGE_WIDTH = 1681
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_4_SECTION.PREVIEW_IMAGE_HEIGHT = 1626
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_4_SECTION.PREVIEW_IMAGE_TYPE = JPEG
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_4_SECTION.PREVIEW_IMAGE_WIDTH = 688
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_5_SECTION.STAGEPOSMAP_IMAGE_HEIGHT = 156
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_5_SECTION.STAGEPOSMAP_IMAGE_TYPE = PNG
INFO [6568] Metadata: mirax.NONHIERLAYER_1_LEVEL_5_SECTION.STAGEPOSMAP_IMAGE_WIDTH = 54
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.AVEGARE_IMAGE_OVERLAP_X_IN_PIXELS =<PHONE_NUMBER>27536
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.AVEGARE_IMAGE_OVERLAP_Y_IN_PIXELS =<PHONE_NUMBER>27536
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.CAMERA_ROTATION = 0.027978956316582
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.CaseCenterUserName = Administrator Administrator
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.IccProfileColorScheme = 0
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.IccProfileGamma = 2
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.IccProfileWhitePoint = 0
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.OBJECT_GUIDE_HYSTERESIS_X = 60
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.OBJECT_GUIDE_HYSTERESIS_Y = 60
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.SCANNED_FOV_COUNT = 1506
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.SCANNER_CAMERA_TYPE = Point Grey GS3-U3-51S5M-C
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.SCANNER_HARDWARE_ID = SC150-210905
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.SCANNER_HARDWARE_VERSION = Pannoramic SCAN 150
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.SCANNER_SOFTWARE_VERSION = <IP_ADDRESS>910
INFO [6568] Metadata: mirax.NONHIERLAYER_1_SECTION.SCANNING_TIME_IN_SEC = 378
INFO [6568] Metadata: mirax.NONHIERLAYER_2_SECTION.DATA_FORMAT_VERSION = 258
INFO [6568] Metadata: mirax.NONHIERLAYER_3_SECTION.VIMSLIDE_HISTOGRAM_DATA_CHANNEL_NUM = 3
INFO [6568] Metadata: mirax.NONHIERLAYER_3_SECTION.VIMSLIDE_HISTOGRAM_DATA_CHANNEL_SIZE = 256
INFO [6568] Metadata: mirax.NONHIERLAYER_3_SECTION.VIMSLIDE_HISTOGRAM_DATA_FORMAT_VERSION = 257
INFO [6568] Metadata: mirax.NONHIERLAYER_5_LEVEL_1_SECTION.SCANINFO_CONCAT_FACTOR = 32
INFO [6568] Metadata: mirax.NONHIERLAYER_5_LEVEL_1_SECTION.SCANINFO_FORMAT_VERSION = 1
INFO [6568] Metadata: mirax.NONHIERLAYER_5_LEVEL_1_SECTION.SCANINFO_TABLE_HEIGHT = 156
INFO [6568] Metadata: mirax.NONHIERLAYER_5_LEVEL_1_SECTION.SCANINFO_TABLE_WIDTH = 54
INFO [6568] Metadata: openslide.background-color = FFFFFF
INFO [6568] Metadata: openslide.bounds-height = 198400
INFO [6568] Metadata: openslide.bounds-width = 85760
INFO [6568] Metadata: openslide.bounds-x = 1536
INFO [6568] Metadata: openslide.bounds-y = 9216
INFO [6568] Metadata: openslide.level-count = 10
INFO [6568] Metadata: openslide.level[0].downsample = 1
INFO [6568] Metadata: openslide.level[0].height = 208128
INFO [6568] Metadata: openslide.level[0].tile-height = 256
INFO [6568] Metadata: openslide.level[0].tile-width = 256
INFO [6568] Metadata: openslide.level[0].width = 88064
INFO [6568] Metadata: openslide.level[1].downsample = 2
INFO [6568] Metadata: openslide.level[1].height = 104064
INFO [6568] Metadata: openslide.level[1].tile-height = 256
INFO [6568] Metadata: openslide.level[1].tile-width = 256
INFO [6568] Metadata: openslide.level[1].width = 44032
INFO [6568] Metadata: openslide.level[2].downsample = 4
INFO [6568] Metadata: openslide.level[2].height = 52032
INFO [6568] Metadata: openslide.level[2].tile-height = 256
INFO [6568] Metadata: openslide.level[2].tile-width = 256
INFO [6568] Metadata: openslide.level[2].width = 22016
INFO [6568] Metadata: openslide.level[3].downsample = 8
INFO [6568] Metadata: openslide.level[3].height = 26016
INFO [6568] Metadata: openslide.level[3].tile-height = 256
INFO [6568] Metadata: openslide.level[3].tile-width = 256
INFO [6568] Metadata: openslide.level[3].width = 11008
INFO [6568] Metadata: openslide.level[4].downsample = 16
INFO [6568] Metadata: openslide.level[4].height = 13008
INFO [6568] Metadata: openslide.level[4].tile-height = 256
INFO [6568] Metadata: openslide.level[4].tile-width = 256
INFO [6568] Metadata: openslide.level[4].width = 5504
INFO [6568] Metadata: openslide.level[5].downsample = 32
INFO [6568] Metadata: openslide.level[5].height = 6504
INFO [6568] Metadata: openslide.level[5].tile-height = 256
INFO [6568] Metadata: openslide.level[5].tile-width = 256
INFO [6568] Metadata: openslide.level[5].width = 2752
INFO [6568] Metadata: openslide.level[6].downsample = 64
INFO [6568] Metadata: openslide.level[6].height = 3252
INFO [6568] Metadata: openslide.level[6].tile-height = 256
INFO [6568] Metadata: openslide.level[6].tile-width = 256
INFO [6568] Metadata: openslide.level[6].width = 1376
INFO [6568] Metadata: openslide.level[7].downsample = 128
INFO [6568] Metadata: openslide.level[7].height = 1626
INFO [6568] Metadata: openslide.level[7].tile-height = 256
INFO [6568] Metadata: openslide.level[7].tile-width = 256
INFO [6568] Metadata: openslide.level[7].width = 688
INFO [6568] Metadata: openslide.level[8].downsample = 256
INFO [6568] Metadata: openslide.level[8].height = 813
INFO [6568] Metadata: openslide.level[8].tile-height = 256
INFO [6568] Metadata: openslide.level[8].tile-width = 256
INFO [6568] Metadata: openslide.level[8].width = 344
INFO [6568] Metadata: openslide.level[9].downsample = 512
INFO [6568] Metadata: openslide.level[9].height = 406
INFO [6568] Metadata: openslide.level[9].tile-height = 256
INFO [6568] Metadata: openslide.level[9].tile-width = 256
INFO [6568] Metadata: openslide.level[9].width = 172
INFO [6568] Metadata: openslide.mpp-x = 0.249710957804617
INFO [6568] Metadata: openslide.mpp-y = 0.249968497983871
INFO [6568] Metadata: openslide.objective-power = 20
INFO [6568] Metadata: openslide.quickhash-1 = b575fd83dbfd7d0b23af07419b9d96fe2b4c6cb054a7ad1e5628e3da1f29de59
INFO [6568] Metadata: openslide.vendor = mirax
INFO [6568] WSI has 10 levels
INFO [6568] Checking level 0
INFO [6568] WSI level 0 has size 88064x208128 and 69918 MB adding..
INFO [6568] Setting tile width and height to 256 256
INFO [6568] Checking level 1
INFO [6568] WSI level 1 has size 44032x104064 and 17479 MB adding..
INFO [6568] Setting tile width and height to 256 256
INFO [6568] Checking level 2
INFO [6568] WSI level 2 has size 22016x52032 and 4369 MB adding..
INFO [6568] Setting tile width and height to 256 256
INFO [6568] Checking level 3
INFO [6568] WSI level 3 has size 11008x26016 and 1092 MB adding..
INFO [6568] Setting tile width and height to 256 256
INFO [6568] Checking level 4
INFO [6568] WSI level 4 has size 5504x13008 and 273 MB adding..
INFO [6568] Setting tile width and height to 256 256
INFO [6568] Checking level 5
INFO [6568] WSI level 5 has size 2752x6504 and 68 MB adding..
INFO [6568] Setting tile width and height to 256 256
INFO [6568] Checking level 6
INFO [6568] WSI level 6 has size 1376x3252 and 17 MB adding..
INFO [6568] Setting tile width and height to 256 256
INFO [6568] Checking level 7
INFO [6568] WSI level was less than 4 MB, skipping..
count:0
calling insert renderer
INFO [6568] EXECUTING EmptyProcessObject because PO is modified.
INFO [6568] EXECUTING ImagePyramidRenderer because PO is modified.
INFO [6568] Recalculating the camera of the view
INFO [6568] Finished initializing OpenGL
finished insert renderer
INFO [6568] Recalculating the camera of the view
INFO [6568] Finished initializing OpenGL
vendor format: mirax
Magn lvl: 20
INFO [6568] EXECUTING EmptyProcessObject because PO is modified.
INFO [6568] EXECUTING ImageChannelConverter because PO is modified.

Log for Tiff:
INFO [26620] Loaded configuration file: C:/Program Files/FastPathology/bin/fast_configuration.txt
INFO [26620] Test data path: C:/ProgramData/FAST/data/
INFO [26620] Kernel source path: C:/Program Files/FastPathology/bin//..//kernels/
INFO [26620] Kernel binary path: C:/ProgramData/FAST/kernel_binaries/
INFO [26620] Documentation path: C:/Program Files/FastPathology/bin//..//doc/
INFO [26620] Pipeline path: C:/ProgramData/FAST/pipelines/
INFO [26620] Qt plugins path: C:/Program Files/FastPathology/bin//..//plugins/
INFO [26620] Library path: C:/Program Files/FastPathology/bin//..//bin/
INFO [26620] Creating new QApp
INFO [26620] Creating new GL context for computation thread
INFO [26620] Large screen detected with width: 3840
Temporary path (UPDATED!): C:/Users/Pradeep/AppData/Local/Temp/fastpathology-gxOXMW
Does folder exist:1
Current temporary project folder location:C:/Users/Pradeep/AppData/Local/Temp/fastpathology-gxOXMW/project_17409488
INFO [26620] QApp already exists..
INFO [26620] Found 1 OpenCL platforms.
INFO [26620] 1 platforms selected for inspection.
INFO [26620] Platform 0: NVIDIA Corporation
INFO [26620] This platform has 1 available devices in total
INFO [26620] Looking for GPU devices only.
INFO [26620] 1 selected.
INFO [26620] Inspecting device 0 with the name NVIDIA GeForce RTX 3080
INFO [26620] There are 1 devices that can be associated with the GL context
INFO [26620]<PHONE_NUMBER>095750 -<PHONE_NUMBER>095750
INFO [26620] Device has OpenGL interop capability
INFO [26620] The device was accepted.
INFO [26620] NVIDIA GeForce RTX 3080 has 68 compute units
INFO [26620] The device NVIDIA GeForce RTX 3080 got a score of 1000068
INFO [26620] The platform NVIDIA CUDA was selected as the best platform.
INFO [26620] A total of 1 devices were selected for the context from this platform:
INFO [26620] The best device was: NVIDIA GeForce RTX 3080
INFO [26620] The following device was selected as main device: NVIDIA GeForce RTX 3080
INFO [26620] Writing directly to 3D textures/images is NOT supported on main device
INFO [26620] Resizing window to 1024 1024
INFO [26620] Window not minimized; turning ON synchronized rendering
INFO [26620] Trying to start computation thread
INFO [26620] Computation thread started
INFO [26620] Drag event received in window widget
INFO [26620] Drop event received in window widget
INFO [26620] Dropped file:D:/Colon_sections/andre_mrxs/slide_export_slide_export/qupath_export_tif/vps_converted/slide_export_qupath.ome_converted.tiff
Selected file: D:/Colon_sections/andre_mrxs/slide_export_slide_export/qupath_export_tif/vps_converted/slide_export_qupath.ome_converted.tiff
INFO [26620] EXECUTING WholeSlideImageImporter because PO is modified.
INFO [26620] Metadata: openslide.comment = <?xml version="1.0" encoding="UTF-8" standalone="no"?><!-- Warning: this comment is an OME-XML metadata block, which contains crucial dimensional parameters and other important metadata. Please edit cautiously (if at all), and back up the original data before doing so. For more information, see the OME-TIFF web site: https://docs.openmicroscopy.org/latest/ome-model/ome-tiff/. --><OME xmlns="http://www.openmicroscopy.org/Schemas/OME/2016-06" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Creator="OME Bio-Formats 6.7.0" UUID="urn:uuid:77f06cca-13c9-4806-b4bb-1e77b7eabbd9" xsi:schemaLocation="http://www.openmicroscopy.org/Schemas/OME/2016-06 http://www.openmicroscopy.org/Schemas/OME/2016-06/ome.xsd"><Image ID="Image:0"><Pixels BigEndian="true" DimensionOrder="XYCZT" ID="Pixels:0" Interleaved="true" PhysicalSizeX="0.249710957804617" PhysicalSizeXUnit="┬╡m" PhysicalSizeY="0.249968497983871" PhysicalSizeYUnit="┬╡m" SizeC="3" SizeT="1" SizeX="85760" SizeY="198400" SizeZ="1" Type="uint8"><Channel ID="Channel:0" SamplesPerPixel="3"><LightPath/></Channel><TiffData FirstC="0" FirstT="0" FirstZ="0" IFD="0" PlaneCount="1"><UUID FileName="slide_export_qupath.ome.tif">urn:uuid:77f06cca-13c9-4806-b4bb-1e77b7eabbd9</UUID></TiffData></Pixels></Image><StructuredAnnotations><MapAnnotation ID="Annotation:Resolution:0" Namespace="openmicroscopy.org/PyramidResolution"><Value/></MapAnnotation></StructuredAnnotations></OME>
INFO [26620] Metadata: openslide.level-count = 12
INFO [26620] Metadata: openslide.level[0].downsample = 1
INFO [26620] Metadata: openslide.level[0].height = 198400
INFO [26620] Metadata: openslide.level[0].tile-height = 128
INFO [26620] Metadata: openslide.level[0].tile-width = 128
INFO [26620] Metadata: openslide.level[0].width = 85760
INFO [26620] Metadata: openslide.level[10].downsample = 1030.6161433297957
INFO [26620] Metadata: openslide.level[10].height = 193
INFO [26620] Metadata: openslide.level[10].tile-height = 128
INFO [26620] Metadata: openslide.level[10].tile-width = 128
INFO [26620] Metadata: openslide.level[10].width = 83
INFO [26620] Metadata: openslide.level[11].downsample = 2079.1869918699185
INFO [26620] Metadata: openslide.level[11].height = 96
INFO [26620] Metadata: openslide.level[11].tile-height = 128
INFO [26620] Metadata: openslide.level[11].tile-width = 128
INFO [26620] Metadata: openslide.level[11].width = 41
INFO [26620] Metadata: openslide.level[1].downsample = 2
INFO [26620] Metadata: openslide.level[1].height = 99200
INFO [26620] Metadata: openslide.level[1].tile-height = 128
INFO [26620] Metadata: openslide.level[1].tile-width = 128
INFO [26620] Metadata: openslide.level[1].width = 42880
INFO [26620] Metadata: openslide.level[2].downsample = 4
INFO [26620] Metadata: openslide.level[2].height = 49600
INFO [26620] Metadata: openslide.level[2].tile-height = 128
INFO [26620] Metadata: openslide.level[2].tile-width = 128
INFO [26620] Metadata: openslide.level[2].width = 21440
INFO [26620] Metadata: openslide.level[3].downsample = 8
INFO [26620] Metadata: openslide.level[3].height = 24800
INFO [26620] Metadata: openslide.level[3].tile-height = 128
INFO [26620] Metadata: openslide.level[3].tile-width = 128
INFO [26620] Metadata: openslide.level[3].width = 10720
INFO [26620] Metadata: openslide.level[4].downsample = 16
INFO [26620] Metadata: openslide.level[4].height = 12400
INFO [26620] Metadata: openslide.level[4].tile-height = 128
INFO [26620] Metadata: openslide.level[4].tile-width = 128
INFO [26620] Metadata: openslide.level[4].width = 5360
INFO [26620] Metadata: openslide.level[5].downsample = 32
INFO [26620] Metadata: openslide.level[5].height = 6200
INFO [26620] Metadata: openslide.level[5].tile-height = 128
INFO [26620] Metadata: openslide.level[5].tile-width = 128
INFO [26620] Metadata: openslide.level[5].width = 2680
INFO [26620] Metadata: openslide.level[6].downsample = 64
INFO [26620] Metadata: openslide.level[6].height = 3100
INFO [26620] Metadata: openslide.level[6].tile-height = 128
INFO [26620] Metadata: openslide.level[6].tile-width = 128
INFO [26620] Metadata: openslide.level[6].width = 1340
INFO [26620] Metadata: openslide.level[7].downsample = 128
INFO [26620] Metadata: openslide.level[7].height = 1550
INFO [26620] Metadata: openslide.level[7].tile-height = 128
INFO [26620] Metadata: openslide.level[7].tile-width = 128
INFO [26620] Metadata: openslide.level[7].width = 670
INFO [26620] Metadata: openslide.level[8].downsample = 256
INFO [26620] Metadata: openslide.level[8].height = 775
INFO [26620] Metadata: openslide.level[8].tile-height = 128
INFO [26620] Metadata: openslide.level[8].tile-width = 128
INFO [26620] Metadata: openslide.level[8].width = 335
INFO [26620] Metadata: openslide.level[9].downsample =<PHONE_NUMBER>1987335
INFO [26620] Metadata: openslide.level[9].height = 387
INFO [26620] Metadata: openslide.level[9].tile-height = 128
INFO [26620] Metadata: openslide.level[9].tile-width = 128
INFO [26620] Metadata: openslide.level[9].width = 167
INFO [26620] Metadata: openslide.quickhash-1 = 13892f3e1fe127fa4a19b980ea46c1e225a09f5f9d352cffdb7972e1712f0d5f
INFO [26620] Metadata: openslide.vendor = generic-tiff
INFO [26620] Metadata: tiff.ImageDescription = <?xml version="1.0" encoding="UTF-8" standalone="no"?><!-- Warning: this comment is an OME-XML metadata block, which contains crucial dimensional parameters and other important metadata. Please edit cautiously (if at all), and back up the original data before doing so. For more information, see the OME-TIFF web site: https://docs.openmicroscopy.org/latest/ome-model/ome-tiff/. --><OME xmlns="http://www.openmicroscopy.org/Schemas/OME/2016-06" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Creator="OME Bio-Formats 6.7.0" UUID="urn:uuid:77f06cca-13c9-4806-b4bb-1e77b7eabbd9" xsi:schemaLocation="http://www.openmicroscopy.org/Schemas/OME/2016-06 http://www.openmicroscopy.org/Schemas/OME/2016-06/ome.xsd"><Image ID="Image:0"><Pixels BigEndian="true" DimensionOrder="XYCZT" ID="Pixels:0" Interleaved="true" PhysicalSizeX="0.249710957804617" PhysicalSizeXUnit="┬╡m" PhysicalSizeY="0.249968497983871" PhysicalSizeYUnit="┬╡m" SizeC="3" SizeT="1" SizeX="85760" SizeY="198400" SizeZ="1" Type="uint8"><Channel ID="Channel:0" SamplesPerPixel="3"><LightPath/></Channel><TiffData FirstC="0" FirstT="0" FirstZ="0" IFD="0" PlaneCount="1"><UUID FileName="slide_export_qupath.ome.tif">urn:uuid:77f06cca-13c9-4806-b4bb-1e77b7eabbd9</UUID></TiffData></Pixels></Image><StructuredAnnotations><MapAnnotation ID="Annotation:Resolution:0" Namespace="openmicroscopy.org/PyramidResolution"><Value/></MapAnnotation></StructuredAnnotations></OME>
INFO [26620] Metadata: tiff.ResolutionUnit = centimeter
INFO [26620] Metadata: tiff.XResolution = 40046.30078125
INFO [26620] Metadata: tiff.YResolution = 40005.0390625
INFO [26620] WSI has 12 levels
INFO [26620] Checking level 0
INFO [26620] WSI level 0 has size 85760x198400 and 64906 MB adding..
INFO [26620] Setting tile width and height to 128 128
INFO [26620] Checking level 1
INFO [26620] WSI level 1 has size 42880x99200 and 16226 MB adding..
INFO [26620] Setting tile width and height to 128 128
INFO [26620] Checking level 2
INFO [26620] WSI level 2 has size 21440x49600 and 4056 MB adding..
INFO [26620] Setting tile width and height to 128 128
INFO [26620] Checking level 3
INFO [26620] WSI level 3 has size 10720x24800 and 1014 MB adding..
INFO [26620] Setting tile width and height to 128 128
INFO [26620] Checking level 4
INFO [26620] WSI level 4 has size 5360x12400 and 253 MB adding..
INFO [26620] Setting tile width and height to 128 128
INFO [26620] Checking level 5
INFO [26620] WSI level 5 has size 2680x6200 and 63 MB adding..
INFO [26620] Setting tile width and height to 128 128
INFO [26620] Checking level 6
INFO [26620] WSI level 6 has size 1340x3100 and 15 MB adding..
INFO [26620] Setting tile width and height to 128 128
INFO [26620] Checking level 7
INFO [26620] WSI level was less than 4 MB, skipping..
count:0
calling insert renderer
INFO [26620] EXECUTING EmptyProcessObject because PO is modified.
INFO [26620] EXECUTING ImagePyramidRenderer because PO is modified.
INFO [26620] Recalculating the camera of the view
INFO [26620] Finished initializing OpenGL
finished insert renderer
INFO [26620] Recalculating the camera of the view
INFO [26620] Finished initializing OpenGL
vendor format: generic-tiff
INFO [26620] EXECUTING EmptyProcessObject because PO is modified.
INFO [26620] EXECUTING ImageChannelConverter because PO is modified.

A 20X objective was used as far as I can tell.

Also, for the TIFF image, the segmentation looks OK, was this without extracting the H-image?

Yea, I did not extract the H-image. It works quite well on the original image without separating stains. It does pick up some smaller patches and areas without epithelia, but pretty good otherwise.. However, I haven't tested it on different combinations of markers yet.

Just from naively reading the prompts, I see no reason why it would produce such strange predictions on an image from the MRXS format, compared to the TIFF format. Strange indeed.
I guess I would need to see one of those images and do some checks. Hence, please share one or two of those images, and I can see if I can find the issue. Please share both the TIFF and MRXS, as you said it worked on the MXRS format.

Could you send me your email so I can send a link to the data download?
My email is rajasekhar.p at wehi.edu.au.. You can also shoot me an email if you don't like to post it publicly..
Can't post a link here to the dataset, but allowed to share it via email.

My e-mail is made publicly available on my user profile<EMAIL_ADDRESS>

Apologies I didn't realize that. Thanks for that!
Well send you a link soon..

But does that mean that extracting the H image was not necessary? The main reason why you were getting worse performance was due to using the MXRS format directly (instead of the TIFF format), which produced some strange predictions?
What I will do for sanity checking, is to try to read patches using openslide in python, and see if there is a difference between the patches, when extracting from the assumed same patch level. I will also see if I get the same behaviour as you get in FP, of course

In this case using the whole WSI without deconvolution worked, but  I'm not
sure if it will always work for other images with DAB brown as we are going
to try a panel of different markers that will label different cells and
compartments in the tissue.. The channel that will be consistent across all
is probably going to be H channel. however, I will try the whole image
first before trying H channel Everytime.
Yes, I get worse performance when using MRXS directly instead of the tiff
format.
Thanks. That approach using python makes sense. Let me know if there is
anything else I can try to troubleshoot so it makes it easier for you. I
appreciate you're busy, so thanks for responding promptly..
On Mon, Jan 17, 2022, 23:57 André Pedersen @.***> wrote:

But does that mean that extracting the H image was not necessary? The main
reason why you were getting worse performance was due to using the MXRS
format directly (instead of the TIFF format), which produced some strange
predictions?
What I will do for sanity checking, is to try to read patches using
openslide in python, and see if there is a difference between the patches,
when extracting from the assumed same patch level. I will also see if I get
the same behaviour as you get in FP, of course
—
Reply to this email directly, view it on GitHub
https://github.com/AICAN-Research/FAST-Pathology/issues/13#issuecomment-1014498162,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJQ2IQGZLBJXRVVDAXUHFLUWQG2JANCNFSM5MDNGORA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Interesting. I have been quite busy lately on my PhD work, and therefore have not had any time to provide an H-image extractor for you, but I can look into this later this week. In order to use this you will have to use Pipelines instead of methods added to the Process widget. I can give you guidelines on how to import it and use it in your workflow, when I have it ready.
How is it going with training segmentation models in MIB? Are you getting any further? Also, have you gotten a trained model yet which you have imported into FP and is using for inference to produce predictions you can import to QuPath?
I guess you saw that I have added multi-class support for two of the scripts relevant for our pipeline (therefore, you can now train multi-class models and deploy them with FP without any issues):

import of pyramidal TIFF predictions from FP into QuPath:
https://github.com/andreped/NoCodeSeg/issues/1#issuecomment-1013309742

export of annotated WSIs as image tiles with corresponding annotation tiles:
https://github.com/andreped/NoCodeSeg/issues/4#issuecomment-1013515084

Only tile import from MIB to QuPath remains, which is not detrimental as long as you can import predictions from FP (it is actually better to import predictions from FP than from MIB, if you want to run inference on a full WSI). Therefore, it has not been prioritized. It is also more tricky to add support for.

@pr4deepr I guess you saw my reply on mail.
In conclusion, having support for the raw mrxs format is outside the scope of our software, as this is a formatting issue the developers of the mrxs format themselves and/or OpenSlide should fix. You will likely have the same issues in QuPath, if you were to use the format directly, unless Peter Bankhead found some fix and integrated it. To read more about the issue, see this thread.
However, I would recommend converting your WSIs to a non-properitary format, which should make it easier to use them in the future. Alternatively, you could look into fixing the mrxs format using 3DHistech's slide converter, which produces the same format, but fixes the encoding issue (Info on the software can be found here).

Hi @andreped
Thanks, I did see the reply today.
Appreciate your help in this matter. We do use 3DHistech's slide converter to export the slides from mrxs to mrxs format.. This is the file we have been working on.
So, QuPath does open MRXS files and it seems to work fine in our hands in QuPath. But, it is possible that there could be compatibility issues down the line.
I will stick to converting WSIs to a non-proprietary format. Will make life easier in the long run.

I could add an option to include uint 0 in the glass class to be filtered.
Just curious is this worth adding for FastPathology?

Also, as a note vips does allow conversion of mrxs to pyramidal tiffs, I just realised it yesterday. It can be a bit slow sometimes..
Cheers
Pradeep

Just curious is this worth adding for FastPathology?

@pr4deepr If glass-rich regions are imputed with 0 integers then yes. Filtering redundant patches makes inference a lot faster. You probably found that inference on the full mrxs WSI in FP was quite slow. That is because all black regions are assumed to be tissue. I will attempt to add a fix before the weekend, but might a week until it is added to the official release of FP, as it requires that FAST is updated first.

Also, as a note vips does allow conversion of mrxs to pyramidal tiffs, I just realised it yesterday. It can be a bit slow sometimes..

 Reading and writing large images from disk is rarely fast. Honestly, I was surprised it wasn't even slower the first time I did it :P
But was the mrxs format the default format that you got from the scanner, or was it stored in another format? If it is NDPI, then it is already supported. We are also working on adding support for Olympus' CellSens VSI, which hopefully will be added in the upcoming release of FP.

@pr4deepr I have now added a fix such that the zero-padded background is included into the glass class, which means that patches containing either lots of glass or the zero-padded regions are neglected.
This should speed up inference on your data by quite a bit!
The solution is not ready yet, but I have made a PR #153 to FAST. When it has been merged, a new release of FAST will be made, and then I will add these changes to FP. Will let you know when it is ready for you to try :]

Thanks a lot for the update @andreped.
Looking forward to the new release.

 Reading and writing large images from disk is rarely fast. Honestly, I was surprised it wasn't even slower the first time I did it :P

Actually, converting larger tiffs to pyramidal tiffs using vips is faster than converting comparatively smaller mrxs files, but I don't if the file being tiff in the first place helps or if its to do with mrxs file.

But was the mrxs format the default format that you got from the scanner, or was it stored in another format?

The mrxs files we used are the ones exported using the 3D Histech converter. Essentially, the slide scanner acquires the images as mrxs files and stores it on a server. We use the 3D histech software to export and convert the files from mrxs to mrxs.
Cheers
Pradeep

@pr4deepr Just wanted to ask one last time if you were able to use FP as you would want using the mrxs files? I believe it should work if you were able to reformat the files, using the 3DHistech converter tool.
Could you try if they work in the new release of FP?

@pr4deepr any update?

Was having some trouble with running TensorRT installation on Windows.
I'm still having same issue as my first post on mrxs files reformatted using the 3DHistech converter tool.
Now, when I convert mrxs to tiff using the 3DHistech exporter and load tis converted tiff into FP, I get this error:
INFO [11568] EXECUTING WholeSlideImageImporter because PO is modified.INFO [4216] Buffer thread in ImagePyramidRenderer stopped

INFO [4216] Buffer thread in SegmentationRenderer stopped
INFO [11568] Metadata: openslide.comment =
85760x198400 (256x256) Lossless compression (DEFLATE)|Date = 26/11/2021|Time = 15:56:12|MPP = 0.24984|3dh_PixelSizeX = 0.249711|3dh_PixelSizeY = 0.249968|3dh_Filter = Default|3dh_Profile = Routine x20|3dh_ScannerHardwareID = SC150-210905
INFO [11568] Metadata: openslide.level-count = 1
INFO [11568] Metadata: openslide.level[0].downsample = 1
INFO [11568] Metadata: openslide.level[0].height = 198400
INFO [11568] Metadata: openslide.level[0].tile-height = 256
INFO [11568] Metadata: openslide.level[0].tile-width = 256
INFO [11568] Metadata: openslide.level[0].width = 85760
INFO [11568] Metadata: openslide.vendor = generic-tiff
INFO [11568] Metadata: tiff.ImageDescription =
85760x198400 (256x256) Lossless compression (DEFLATE)|Date = 26/11/2021|Time = 15:56:12|MPP = 0.24984|3dh_PixelSizeX = 0.249711|3dh_PixelSizeY = 0.249968|3dh_Filter = Default|3dh_Profile = Routine x20|3dh_ScannerHardwareID = SC150-210905
INFO [11568] Metadata: tiff.ResolutionUnit = centimeter
INFO [11568] Metadata: tiff.XResolution = 40046.315104895104
INFO [11568] Metadata: tiff.YResolution = 40005.284044336811
INFO [11568] WSI has 1 levels
INFO [11568] Checking level 0
INFO [11568] WSI level 0 has size 85760x198400 and 64906 MB adding..
INFO [11568] Setting tile width and height to 256 256
count:0
calling insert renderer
INFO [11568] EXECUTING EmptyProcessObject because PO is modified.INFO [4216] EXECUTING EmptyProcessObject because PO is modified.

INFO [11568] EXECUTING ImagePyramidRenderer because PO is modified.
INFO [11568] Recalculating the camera of the view
INFO [11568] Finished initializing OpenGL
finished insert renderer
INFO [11568] Recalculating the camera of the view
INFO [11568] Finished initializing OpenGL
vendor format: generic-tiff
ERROR [11568] FAST exception caught in Qt event handler Image level is too large to convert into a FAST image

Converting the tiff exported from 3DHistech into pyramidal tiff via vips seems to solve this problem.
Hope this is helpful.

Running inference using OpenVINO should be quite fast, but that uses either the integrated GPU (Intel) or CPU. Most likely the pathologists that you are working with does not have a machine with GPU, and therefore OpenVINO is probably the most optimal inference engine. TensorRT only works with dedicated GPUs (NVIDIA).
Regarding the TIFF image you are testing. Note that there is only registered 1 level, which means that it is not pyramidal, as you mentioned. FAST depend on having image planes that can actually get kept in memory. What QuPath does is to pyramidarize the image for you, and therefore you might be able to read it there, but in general, I would suggest working with pyramidal, tiled images. Makes life easier for you, Pete, us, and everyone.
But then I believe our platform can read the mrxs format, given that it is stored in a pyramidal, tiled format, and that 3DHistech has not corrupted their own format (which they are also able to fix, in a separate software/plugin).
Since this problem is solved, I will close this issue, but feel free to reopen it again, if you are getting new issues with the format. However, most of the troubles you had were outside the scope of what we can do in FAST/FP.

Thanks..
Yes, FP can read mrxs which is great!
QuPath takes a while to save as pyramidal tiffs, so vips is the best solution for that.
Just adding this here for future reference
what doesn't work:
mrxs -> export to mrxs using 3D Histech  -> prediction problems in FP
mrxs -> export to tiff using 3D Histech -> Not pyramidal, doesn't work in FP
what works:
mrxs ->export to tiff using 3D Histech -> convert to pyramidal tiff using QuPath or vips -> works in FP
Thanks for all the help @andreped .. Appreciate it!


Future-proofing for Tailwind v2.0

As discussed in #114, we might wanna include this to future-proof for v2.0.
source - Upcoming Changes

Pointed to the wrong repo, duh. 🤦♂

I revisited this as part of 4.3.0


fix offline transactions issue

Offline Transaction page need a node url to be able to mock transaction data
Old Behavior: - Wallet is not able to fetch nodes from statistics service and end up with one node in storage which get filtered and emptied before mocking the data.
Introduced solution:

Query the storage to get urls to which that profile was previously connected and use them to mock the needed data.
In case the wallet is never connected to the internet use a fake node to mock repositories and display UI correctly.

Basic scenario is: Wallet is always offline. So no node URL should be required to load offline transactions view.

Turn off Internet.
Open wallet in incognito (no history)
Create new profile
Logout
Go to offline transactions view.

Result: You have error:

When Internet is ON it started to working but main use case is when Internet is always off on computer.

@bassemmagdy @cryptoBeliever with latest update it works for me

@bassemmagdy @cryptoBeliever with latest update it works for me

Same for me.


fix log error for svc event watch

@jojimt  PTAL.

Diff looks good. Will merge once sanity passes.


How about add BN after each expanded Conv layer

Very interesting work! I'm curious why not add BN after each extended CONV layer. I don't know if it can bring improvement.

Hi, we have tried to add BN, however, in most cases, it didn't help, even got slightly worse results than without bn.

Very interesting work! I'm curious why not add BN after each extended CONV layer. I don't know if it can bring improvement.

Hi, we have tried to add BN, however, in most cases, it didn't help, even got slightly worse results than without bn.


Adaptive Card Input.Date not giving required validation when date is deleted after selecting it.

I m using Adaptive card v1.4 and bot framework sdk v4 in .NET.
i have a use case where card to displayed to user which has date field, time field, Description field and a Schedule button. both date and time fields are required.
i m facing the problem with Input.Date element of adaptive card in deployed teams channel. Issue is when we select any date in the date field and if we click on the cross button of date field and remove the date and click on schedule button we should get the required error message validation of the date field. where as i m getting the previously selected date which is not the correct scenario.
how can we resolve this issue.
here is the json of adaptive card.
{
"type": "AdaptiveCard",
"version": "1.4",
"msTeams": {
"width": "Full"
},
"body": [
{
"type": "ColumnSet",
"columns": [
{
"type": "Column",
"items": [
{
"type": "Input.Date",
"id": "reminderDate",
"value": "{DateTime.UtcNow.ToLocalTime():yyyy-MM-dd}",
"min": "{DateTime.UtcNow.ToLocalTime():yyyy-MM-dd}",
"label": "Date",
"isRequired": true,
"errorMessage": "Please enter Date",
"validation": {
"nudgable": true,
"validateOn": "blur",
"min": "2023-05-28",
"errorMessage": "Please select a future Date"
}
}
],
"width": "stretch"
},
{
"type": "Column",
"items": [
{
"type": "Input.Time",
"id": "reminderTime",
"value": "",
"min": "{DateTime.UtcNow.ToLocalTime:HH:mm}",
"placeholder": "select time",
"label": "Time",
"isRequired": true,
"errorMessage": "please enter time",
"validation": {
"nudgable": true,
"validateOn": "blur",
"min": "{DateTime.UtcNow.ToLocalTime():HH:mm}",
"errorMessage": "Please select a future time"
}
}
],
"width": "stretch"
}
],
"spacing": "medium"
},
{
"type": "Input.Text",
"id": "reminderDetails",
"label": "Description",
"isMultiline": true,
"placeholder": "Type Here (100 Characters Max)",
"errorMessage": "Please enter Detail",
"maxLength": 100,
"spacing": "large"
},
{
"type": "ColumnSet",
"columns": [
{
"type": "Column"
},
{
"type": "Column",
"width": "auto",
"items": [
{
"type": "ActionSet",
"actions": [
{
"type": "Action.Submit",
"id": "scheduleButton",
"style": "positive",
"data": {
"remindersubmitted": 1
},
"title": "Schedule"
}
],
"horizontalAlignment": "Right"
}
]
}
]
}
],
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json"
}

Thank you for reporting this, we will check this and get back to you.

We are also able to repro this issue at our end. We also see that min value of Date and time are not reflecting in Web. We are able to select previous date and time.

We have raised a bug for the same. We will keep you posted on the updates. Thank you.


A Important Feature about WebDAV Requested

What feature or improvement do you think would benefit Files?
I found that I can't open my webDAV in this app successfully.It displayed"Did you delete this folder?"when I was trying visiting it.
Also I want win11 icons.You can learn it from "My Files-X"app from ms store.
Requirements
Sorry, I'm a noob in programming
Files Version
<IP_ADDRESS>
Windows Version
Windows 10 22H2 19045.2486
Comments

Merging with #3917
The icons follow Windows you can install an unofficial icon pack (YOU WONT GET SUPPORT DOING THIS) or upgrade to Windows 11


smoothByTolerancePercentage

add new smoothByTolerancePercentage method to Function interface and use it in additive model
@deerzq @saurfang

@deerzq thanks for review, issue addressed

LGTM


It would be better to remove 'display' from the descriptions in 'Rename Quick Access Item' dialog

Storage Explorer Version: 1.35.0-dev (98)
Build Number: 20240712.1
Branch: main
Platform/OS: Windows11/Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.5(Apple M1 Pro)
Architecture: arm64/x64/x64/x64
How Found: From running test cases
Regression From: Not a regression
Steps to Reproduce

Select one ADLS Gen2 storage account -> Pin it to the 'Quick Access' node.
Right click the QA item -> Click 'Rename'.
Observe the description in the rename dialog.

Expected Experience
It would be better to remove 'display' from the description.
It would be better to use an appropriate name instead of 'Display name'.
Actual Experience
It indicates to change the display name.

Additional Context
If using display name in the rename dialog, it doesn't match the display name in the properties.

Changed property name to "Node Display Name". That property is specifically for the node's name as a whole, which includes the status of the thing (aka the part in parens) and the display name of the thing (thing in this case being the quick access item).

Verified this issue on the main build 20240717.2. the property name has been updated to 'Node Display Name'.


Pre-trained models

Great work,
Will you add also the pre-trained models (after B-cosification)?
have a nice day

Hi @SalvatoreRa, yes we plan to also release the pre-trained models.

It sounds great, curious to try them


Question

Is there any distance function that I could use to measure minimum distance (straight line) between a set of imported points/address and natural/ coastline/waterways without using  network tools?
Thanks
Emiliano

@emilianosantin Hi! No pyrosm does not include any of these, but you can use geopandas to calculate distances between objects. One approach is to loop over your point geometries (with apply()) and calculate the distance between the given point to all other geometries (e.g. waterways), and from those find out which is the minimum distance.
There is also some course material about doing nearest neighbor analysis using Python, but these assume that you have two point datasets:
https://autogis-site.readthedocs.io/en/latest/notebooks/L3/06_nearest-neighbor-faster.html

@emilianosantin Hi! No pyrosm does not include any of these, but you can use geopandas to calculate distances between objects. One approach is to loop over your point geometries (with apply()) and calculate the distance between the given point to all other geometries (e.g. waterways), and from those find out which is the minimum distance.
There is also some course material about doing nearest neighbor analysis using Python, but these assume that you have two point datasets:
https://autogis-site.readthedocs.io/en/latest/notebooks/L3/06_nearest-neighbor-faster.html

Thanks for your help!
Sent from my iPhone

On Jan 30, 2021, at 1:53 AM, Henrikki Tenkanen<EMAIL_ADDRESS>wrote:

Closed #107.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks for your help!
Sent from my iPhone

On Jan 30, 2021, at 1:53 AM, Henrikki Tenkanen<EMAIL_ADDRESS>wrote:

Closed #107.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Model::getDateFormat() incorrect for Date columns in MySQL

For every column type, getDateFormat always returns the Schema's timestamp format ('Y-m-d h:m:s'). For a Date column within that schema, it should return just 'Y-m-d'.
In my use case, I'm converting data from an old LMS into proper objects, and the start and end dates of a Semester don't need a time, so I've created those columns as date's, not datetime's. And without using custom mutators, getDirty() believes attributes have changed even though the saved value will be the same.
It's an easy fix to use a mutator on the Model to handle this, but ideally this should be handled by the eloquent model automatically.

Could you send a pull with tests please?


fix(index.d.ts): update init options

:tada: This PR is included in version 1.79.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update _card.scss

Added transition to cards for smoother experience.

Good idea to add more transitions! However, I would like to avoid transition all. What effects actually need transitions?
Additionally, there is a $transition-standard defined in _global.scss, I'd like to continue using this. I'd be fine with changing it from 0.225s ease, as I don't think that was an especially considered choice.

This works well
section.card.card--small.card--link:hover {     z-index: 2;     -webkit-transition: all 120ms ease-in;     -webkit-transform: scale(1.1);     -ms-transition: all 120ms ease-in;     -ms-transform: scale(1.1);     -moz-transition: all 120ms ease-in;     -moz-transform: scale(1.1);     transition: all 120ms ease-in;     transform: scale(1.1); }

@Smurphonomics we are always in a current version of chrome in this app, so no need for additional browser rules. And I would like to avoid transition: all.

I think we can just do:
 transition: transform .1s ease-in-out;c
The scale transform feels very abrupt right now, that's all I wanted to make smoother.

https://github.com/lbryio/lbry-app/commit/7c380ce01b7e9d45399f993a4ade39f9a4adce9d

I saw cross browser SCSS in the app code, so I assumed it was being coded for a web based version also?
A good idea to remove "ALL", as it can have performance issues with it containing hidden code you don't need, catering for ALL properties.
@98farhan94 transition: transform .1s ease-in-out; is much cleaner :)

@98farhan94 For even cleaner and more optimised code, we can omit the "transform" part as everything has already been declared.
``
.card-row > .card {transition: .1s ease-in-out;}

@Smurphonomics Okay, I'll append it in a new merge.

Nope. Forget it. I thought omitting ALL would mean it just used the animation on the scale hover event. But it looks like omitting ALL just sets it to the initial state, which is ALL :(
So keep it to transition: transform .1s ease-in-out; after all :)

Yep, that's basically what we added @Smurphonomics.
Re: cross-browser, it's from the pre-Electron days and should probably be removed.


[bug] fromInt(0xFFFF_FFFF, true) gives 0x1_0000_0000_0000_0000

fromInt(0xFFFF_FFFF, true) gives 0x1_0000_0000_0000_0000
I don't see how this is correct.

Can you elaborate how you are getting 0x1_0000_0000_0000_0000? in my tests fromInt(0xFFFF_FFFF, true) gives 0xFFFF_FFFF_FFFF_FFFF, the same asfromInt(-1, true) as the 0xFFFF_FFFF overflows the integer limit and is assumed as -1. If you wish to get the equivalent of 0xFFFF_FFFF as long number maybe you want to use the fromNumber(0xFFFF_FFFF, true) operation?
const { fromInt, toString } = require('longfn')
console.log(`0x${toString(fromInt(0xFFFF_FFFF, true), 16).toUpperCase()})

This is the same behavior as in long.js. Maybe better documentation is necessary?

Sorry, I was confused. I somehow thought that fromInt was an alias for fromInt32.
Hence I did something like this:
console.log(longfn.toNumber(longfn.fromInt(0xFFFF_FFFF, true)).toString(16))


Example cases

[ ] Create an issue
[ ] Update an issue
[ ] Close an issue (Pull Request is merged)
[ ] Close an issue (Pull Request is closed by Renovate)

Create an Issue

Closed Pull Request: https://github.com/suzuki-shunsuke/example-renovate-issue-action/pull/5
Created Issue: https://github.com/suzuki-shunsuke/example-renovate-issue-action/issues/4
Build Link

Pull Request was closed once because CI failed and it is difficult to solve the problem soon.

Then GitHub Actions Workflow was triggered and renovate-issue-action was run, and an Issue was created.

Update an Issue

Close an issue (Pull Request is merged)

Close an issue (Pull Request is closed by Renovate)


feat: added ability to deploy more than one NIM model.

https://issues.redhat.com/browse/NVPE-15
Description

Ability to deploy more than one NIM model.
How Has This Been Tested?

Tested locally.
Test Impact

Manually tested the UI to confirm that multiple deployed models display accurately.
Verified the Deploy button appears on the Model Serving screen.
Verified the Deploy button appears on the Models tab under Data Science Project
Ensured that Secrets are not getting deleted if more than 1 deployment is present within the same namespace
Ensured that PVC does get deleted regardless of how many deployments are present within the same namespace

Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[x] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/ok-to-test

Looks like if you try to deploy two of the same model it errors out (probably correctly)

But if you then change it and deploy -- it seems to cause issues on deleting. I get an error on delete:
EDIT: different resource name because I forgot to capture the delete modal error first time through
EDIT2: It seems I have orphan PVCs in my namespace after this


Allow schedulers to step after validation

What does this PR do?

Fixes https://github.com/PyTorchLightning/pytorch-lightning/issues/5943
Allows schedulers to step after each time validation is performed. Beneficial when working with large datasets with val_check_interval<1 and using the ReduceLROnPlateau scheduler .
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

Hello @SkafteNicki! Thanks for updating this PR.

In the file pytorch_lightning/trainer/trainer.py:

Line 718:1: W293 blank line contains whitespace

In the file something.py:

Line 125:13: E124 closing bracket does not match visual indentation
Line 128:13: E124 closing bracket does not match visual indentation
Line 276:15: W292 no newline at end of file

In the file tests/trainer/optimization/test_optimizers.py:

Line 478:1: W293 blank line contains whitespace
Line 488:1: W293 blank line contains whitespace
Line 513:1: W293 blank line contains whitespace
Line 515:34: E226 missing whitespace around arithmetic operator

Is there an update on this? Has it been merged already in another PR? Would be useful to me.


Update piptools to avoid reusing InstallRequirement

Update piptools to avoid reusing InstallRequirement

Prevents re-preparation of deleted PKG-INFO files
Fixes #2435

@uranusjr approved verbally so I'm merging


[FEAT] Uninstaller?

I'm trying to remove the software, I downloaded the compressed released version and I am unable to remove the folder cause the AuroraRGB,sys.
How can we remove it totally?

Disable autorun. Restart pc. You can remove it now

Disable autorun. Restart pc. You can remove it now

how to disable the autorun? What if we add an uninstalling section in the README.md?


DGLError: Mutation is not supported in heterograph.

Hi there,
When I try to run the protein graph example from the README I get the following error:
DGLError: Mutation is not supported in heterograph.
According this post If found on google: https://discuss.dgl.ai/t/how-to-add-nodes-edges-to-heterograph/696
adding nodes to heterographs is only supported in dgl > v0.5 but the installation instructions specify version 0.4.3.
Or am I missing something?

Hey @jadechip!
I recall we had some compatibility problems with DGL > 0.5 and so don't explitly support it. As for your error, that's a new error that I haven't come across - I suspect we may only support dgl.DGLGraph.
We've been working on a v2.0 of graphein (check it out on the graphein-api branch!) which I'd encourage you to use as there are many new features & we'll be sunsetting the version on main shortly.  There are some differences as we now build the graphs as networkx graphs and convert these into various geometric DL library formats with a convertor object (graphein.ml.conversion on the conversion branch.  We're a little light on docs at present but we expect to have everything wrapped this week :) If you have the time, it might make sense to hold off until next week - I don't expect any breaking changes but there'll be a fair bit of dev activity this week.
Happy to support via email too :)
Closing this as it's not related to 2.0


Setup DB to store users

Add a Contact Form
Features To Add

[ ] Validate user input for each field
decide between one of these 2
[ ] onSubmit, save user info to MongoDB & send user Message to my email
[ ] integrate mailchimp or something to handle a lot of that for me


use poetry for python dependencies

Provides:

A lock file
Access to all+latest packages on PyPI
Faster version resolution, hopefully

Sticking with mamba for now.


short way to configure feign client

Hi all, I have problem with current Feign Client configuration via Configuration Class.
Currently I create feign client using this way :
@FeignClient(name = "authFeign",
    url = "${service.auth.endpoint}",
    fallbackFactory = AuthFeignFallbackFactory.class,
    configuration = AuthConfiguration.class)
public interface AuthFeign {

}

and every time I create feign client, I create configuration class.
@Configuration
public class AuthConfiguration {

  @Autowired
  private FeignAuthProperties properties;

  @Bean
  public Request.Options options() {
    return new Request.Options(
        (int) properties.getTimeUnit().toMillis(properties.getConnectTimeout()),
        (int) properties.getTimeUnit().toMillis(properties.getReadTimeout())
    );
  }

  @Bean
  public Logger.Level level(){
    return properties.getLevel();
  }

}

Is there any short way to configure feign client just via configuration properties? example :
feign.authFeign.connect-timeout=2000
feign.authFeign.read-timeout=2000
feign.authFeign.log-level=basic

If there is no way to configure feign client via configuration properties, I will happy to contribute to this repository
Best Regards.

I dont believe there are properties for this, but instead of specifying the configuration property for each client, if you want those values to apply to all Feign clients you can just create those beans as part of your applications configuration.

hi @ryanjbaxter , I think it is very helpful if we can also configure default feign client configuration via properties, like :
feign.client.default.connect-timeout=10000
feign.client.default.read-timeout=10000
feign.client.default.logging-level=basic
feign.client.default.retryer=...
feign.client.default.error-decoder=...
feign.client.default.request-interceptors=...

and if we need to create configuration per feign client, we can also override the values
feign.client.default.connect-timeout=10000
feign.client.default.read-timeout=10000
feign.client.default.logging-level=basic
feign.client.default.retryer=...
feign.client.default.error-decoder=...
feign.client.default.request-interceptors=...

feign.client.feignName.connect-timeout=2000
feign.client.feignName.read-timeout=2000
feign.client.feignName.logging-level=headers

this would be an enhancement as far as i know

maybe


Bump. Let's see if we pick up a new systemd.

Desperate attempt to look into podman issue 24220, the
missing-logs-and-events flake. I noticed on 1mt that
rawhide is on systemd-257~rc1, which is what's on
debian, and we haven't seen 24220 on debian. F41
is still on 256.7.
Let's see what this PR brings in. If we get systemd-257
on rawhide, let's hammer at it on podman and see what
happens with 24220.
Also, fix a big duh on my part. My new README-simplified
had a line beginning with the word "timebomb", which
'make timebomb-check' interpreted as an actual timebomb
directive, which caused the check to fail. Workaround
is to shuffle words; a more proper solution might be
to exclude READMEs, or look only in *.sh files, or
some other smart filter.
Signed-off-by: Ed Santiago<EMAIL_ADDRESS>

20241118t130000z-f41f40d13
20241107t210000z-f41f40d13 ⇑ (built in #393)

debian
prior-fedora
fedora
fedora-aws
rawhide

kernel
6.11.7-1
6.8.5-301
6.11.8-300
6.11.7-300
6.12.0-0.rc7.59

6.11.6-1 ⇑

6.11.6-300 ⇑
6.11.6-300 ⇑
6.12.0-0.rc6.20241105git2e1b3cc9d7f7.52 ⇑

aardvark-dns
1.12.2-1
1.12.2-2
1.13.1-1
1.13.1-1
1.13.0-2

1.13.0-1 ⇑
1.13.0-1 ⇑

buildah
1.38.0+ds1-2
1.37.5-1
1.38.0-2
1.37.5-1
1.38.0-2

1.37.5+ds1-1 ⇑
1.37.3-1 ⇑
1.37.5-1 ⇑

1.37.5-1 ⇑

container-selinux
?
2.233.0-1
2.234.2-1
2.234.2-1
2.234.2-1

2.233.0-1 ⇑
2.233.0-1 ⇑
2.233.0-1 ⇑

containers-common
?
0.60.4-2
0.61.0-1
0.60.4-4
0.61.0-1

0.60.4-4 ⇑

0.60.4-5 ⇑

criu
3.19-3
4.0-1
4.0-2
4.0-2
4.0-2

3.19-2 ⇑

golang
2:1.23~2
1.22.7-1
1.23.3-1
1.23.3-1
1.23.3-2

1.23.2-2 ⇑
1.23.2-2 ⇑
1.23.2-2 ⇑

podman
5.3.0+ds1-3
5.2.5-2
5.3.0-1
5.2.5-1
5.3.0-1

5.2.5-1 ⇑
5.2.3-1 ⇑
5.3.0~rc2-1 ⇑

5.3.0~rc2-1 ⇑

runc
1.1.15+ds1-1
1.2.1-1
1.2.1-1
1.2.1-1
1.2.1-1

1.1.12-3 ⇑

1.1.12-4 ⇑

skopeo
1.16.1+ds1-1+b1
1.16.1-1
1.17.0-1
1.16.1-1
1.17.0-1

1.16.1-1 ⇑

1.16.1-2 ⇑

systemd
257~rc2-3
255.13-1
256.8-1
256.8-1
257~rc1-2

257~rc1-3 ⇑

256.7-1 ⇑
256.7-1 ⇑
256.7-1 ⇑

podman - pass.


t265 imu problem

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ t265 }

Firmware Version
<IP_ADDRESS>1

Operating System & Version
Ubunut 16.04

Kernel Version (Linux Only)
4.15.0-112-generic

Platform
PC

SDK Version
librealsense SDK 2.36

Language
C++

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
The sensor of T265 (including IMU) is calibrated on the production line, so no further calibration process is required (unlike the IMU on D435i). However, realsense-viewer shows that the acceleration will vary from 8 to 10 when placed at rest in different directions. Does this have an impact on vio and how to solve it?

Hi @dorodnic can any people help me? thanks!

As far as I know, D435i has the same problem. D435i and T265 share the same imu. After I do rs-imu-calibration on D435i, its acceleration varies from 9.7~9.9, before calibration the range is 8~10. So I guess if I can modify the rs-imu-calibration tool to run on T265, then the problem will be handled. Will update this comment.

@youwyu did it work?