Colony counter and control method

Abstract

The burden on the user when counting colonies is reduced. A colony counting device includes an acquisition section that acquires an image of colonies generated in a test specimen, and an execution section that executes first software, the execution section performing processing for counting the number of colonies based on the image of the colonies. The execution section reads a user file containing information in a matrix format created by second software, different from the first software, to count the colonies generated in the test specimen or to manage a colony count result. Furthermore, the execution section creates a count table used for counting colonies based on the user file.

Description

BACKGROUND OF THE INVENTION 1. TECHNICAL FIELD

[0001] The invention relates to a colony counting device, a control method and a program. 2. DESCRIPTION OF THE STATE OF THE ART

[0002] In a food manufacturing factory, a colony counter is used to test whether or not bacteria are present in a product. A tester creates a culture medium in a Petri dish, places a food sample into the culture medium, and cultivates the food sample in a culture vessel or similar for a predetermined period of time. The tester then removes the Petri dish from the culture vessel and uses the colony counter to count the colonies (bacterial colonies). The accuracy of the colony counter is important for food hygiene management.

[0003] JP 2015-171334 A proposes to count the number of colonies using a Petri dish image taken with a camera.

[0004] Meanwhile, a user creates a test list and a counting table using widely used spreadsheet software, prints the test list and counting table on paper, and cultivates a fungus with a culture medium for each test specimen (sample name) while referring to the test list. The user counts the colonies produced by the fungus visually or with the help of a colony counter. Furthermore, the user manually enters the colony counting result into the counting table. Then, the user opens the original counting table with spreadsheet software and manually enters the counting result of the paper counting table into an electronic file. This process may result in transcription errors, and the transcription work is very laborious for the user.

[0005] Conversely, if a count table is generated by a colony counter capable of displaying an electronic count table, the burden of transcription work is alleviated. In this case, the user must be familiar with the colony counter's user interface to generate the count table, which presents a barrier to colony counter adoption. If, in such a case, a colony counter's count table can be generated using spreadsheet software familiar to the user, the barrier to colony counter adoption is reduced. SUMMARY OF THE INVENTION

[0006] An object of the invention is therefore to reduce the burden on a user when counting colonies.

[0007] For example, the invention provides a colony counting device comprising a detection section configured to detect an image of colonies generated in a test body; and an execution section configured to execute a first software, the execution section being configured to perform counting processing of a number of the colonies from the image of the colonies, wherein the execution section comprises: a reading section configured to read a user file containing information in a matrix format and generated by a second software different from the first software to count the colonies generated in the test body or to manage a colony count result; and a creation section configured to create a counting table used to count colonies based on the user file.

[0008] According to the invention, the burden on the user when counting colonies is reduced. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a view showing a colony counter; Fig. 2 is a diagram for describing an electrical configuration of a head device; Fig. 3 is a diagram for describing an electrical configuration of a control device; Fig. 4 is a view for describing a user interface (UI); Fig. 5 is a view for describing a user interface for creating a count table from a sample database; Fig. 6 is a view describing a user interface for re-creating a count table; Fig. 7 is a view for describing a spreadsheet program; Fig. 8 is a view describing a user interface for adding a column item; Fig. 9 is a view for describing a user interface during a test; Fig. 10 is a view for describing a user interface at the time of instructing a count; Fig. 11 is a view showing a UI at the time of registering a counting result in a cell; Fig. 12 is a view for describing a user interface illustrating automatic identification of a target cell; Fig. 13 is a view for describing a user interface for resetting a counting condition; Fig. 14 is a flowchart illustrating the processing performed by a PC; Fig. Figure 15 is a flowchart illustrating the processing of the sample database; Fig. Figure 16 is a flowchart illustrating a method for counting colonies; Fig. 17 is a view for describing a business file; Fig. 18 is a view describing a configuration file; Fig. 19 is a view for describing a function of each cell; Fig. 20 is a view for describing a counting table; Fig. 21 is a view for describing a counting table; Fig. 22 is a view for describing the reflection of a counting result; Fig. 23 is a view for describing the treatment of an empty cell; Fig. 24 is a view for describing a Petri dish having a plurality of accommodation areas; Fig. 25 is a view for describing a configuration file related to the Petri dish having the plurality of accommodation areas; Fig. 26 is a view for describing a test setting included in the sample DB; Fig. 27 is a view for describing a tag related to averaging; Fig. Fig. 28 is a view for describing a method of converting a configuration file into a count table without using a tag; Fig. 29 is a view for describing the adjustment of a test setting; Fig. 30 is a flowchart illustrating a method for preparing a count table; Fig. 31 is a flowchart illustrating a method for detecting a test setting for a column; and Fig. 32 is a flowchart illustrating a method for detecting a test setting. DETAILED DESCRIPTION

[0009] An embodiment will be described in detail below with reference to the accompanying drawings. It should be noted that the following embodiment does not limit the invention according to the claims, and all feature combinations described in the embodiment are not necessarily essential to the invention. Two or more features from the plurality of features described in the embodiment can be arbitrarily combined. Furthermore, the same or similar configurations are denoted by the same reference numerals, and redundant descriptions are omitted. <Erste Ausführungsform> [Colony counter]

[0010] Fig. Figure 1 shows a colony counter 1. Note that the colony counter 1 includes a head device 1a and a control device (personal computer (PC)) 1b, which will be described later. The head device 1a and the PC 1b can be connected, for example, via a USB (Universal Serial Bus) cable or wirelessly.

[0011] The head device 1a includes an upper unit 2, a support unit 3, and a lower unit 4. A camera and an illumination device are provided inside the head device 1a. The support unit 3 is located between the upper unit 2 and the lower unit 4 and supports the upper unit 2. A table 5 is attached to the top of the lower unit 4. The table 5 is equipped with a transmission window 6 on which a Petri dish 15 is placed, and a positioning member 7 configured to position the Petri dish 15 in the center of the transmission window 6. An operation section 8 and a front camera 10 are provided in front of the lower unit 4. The operation section 8 includes a plurality of switches (e.g., a first operation button 8a, a second operation button 8b, and a third operation button 8c) configured to allow a user to input instructions.The front camera 10 is optional and reads, for example, a two-dimensional symbol (barcode) and the like. The front camera 10 is arranged in a recess 4a provided in a front surface of a housing of the head device 1. A power switch 9 is located on a side surface of the lower unit 4.

[0012] Fig. 2 shows an electrical configuration of the head device 1a. An MCU 20 is a processor that executes a control program 27 stored in a memory device 25 and controls the head device 1a according to the control program 27. MCU is an abbreviation for Micro-Controller Unit. The MCU 20 controls the main camera 11 and the front camera 10 via an imaging control section 21 to acquire various types of image data. The imaging control section 21 controls, for example, the exposure time of the main camera 11. The MCU 20 turns the ring illumination devices 12 and 13 and the coaxial illumination device 14 on or off via an illumination control section 22. The illumination control section 22 controls the drive power to be supplied to the ring illumination devices 12 and 13 and the coaxial illumination device 14.The MCU 20 receives a user input input from the operation section 8 via an operation receiving section 23. The operation receiving section 23 includes an input circuit or the like that generates a signal indicating a state of a switch section of the operation section 8. A communication circuit 24 is a circuit connected to the circuit shown in FIG. Fig. 3 via a communication cable 26. The communication circuit 24 may include a wireless communication circuit and a LAN interface circuit. LAN is an abbreviation for Local Area Network. The communication cable 26 may be, for example, a USB cable. The storage device 25 includes, for example, a read-only memory (ROM) in which the control program 27 is stored and a random access memory (RAM) serving as a work area. The storage device 25 may store, for example, a test condition 28 set by the PC 1b, a test image 29 captured by the main camera 11, and the like. The test condition 28 may include, for example, an illumination condition, an imaging condition, a counting condition, and the like. The test image 29 is an image of the Petri dish 15 containing a culture medium and a sample.

[0013] Fig. 3 shows the PC 1b controlling the head device 1a. An MCU 30 is a processor that executes a program stored in a memory device 35 and controls the PC 1b and the head device 1a according to the program. The MCU 30 receives a user instruction from a keyboard 32 and a pointing device 33 connected to an input / output circuit 31. The MCU 30 controls a printer 38 connected to the input / output circuit 31 to print a table or the like on paper. The MCU 30 displays various types of information on a display device 37 via a display control section 36, such as a graphics card. A communication circuit 34 is a circuit that communicates with the head device 1a via the communication cable 26. The communication circuit 34 may include a wireless communication circuit and a LAN interface circuit.The storage device 35 includes, for example, a read-only memory (ROM) in which a program is stored and a random access memory (RAM) serving as a work area. In addition, the storage device 35 may include a hard disk drive (HDD) and a solid state drive (SSD). The storage device 35 may store an application program 39, the test condition 28, the test image 29, a sample DB 40, a count table 55, and the like. DB is an abbreviation for database. The application program 39 is responsible for, for example, creating and editing the sample DB 40 and the count table 55, controlling the head device 1, and the like. The test condition 28 is set by the MCU 30 according to the application program 39. The test image 29 is received from the head device 1. The sample DB 40 is a database referenced when creating the count table 55.The count table 55 is a table in which a plurality of cells are arranged in an array, and includes a row element and a column element.

[0014] In the PC 1b, the communication circuit 34 can perform wireless communication with a terminal device 1c, such as a smartphone or a tablet. The terminal device 1c can display the counting table 55 or display a test list created from the counting table 55. The test list includes a Petri dish number, a sample name, a bacterial species, a culture medium, a dilution factor, a cultivation time, and the like, and is used when the user prepares a test specimen in the Petri dish 15.

[0015] A spreadsheet program 41 is optional spreadsheet software that is widely used. A business file 200 and a configuration file 210 created by the spreadsheet program 41 will be described in detail in a second embodiment. [Test procedure]

[0016] A general test procedure is as follows. (1) The user creates a test list by hand. The test list consists of multiple lines, and each of these lines can contain a Petri dish number, a bacterial species, a dilution factor, a counting number, and a comment (sample product name, etc.). Note that the Petri dish number referred to here is identification information assigned in advance according to a predetermined rule to specify a cultivation condition such as a culture medium type or a dilution factor. (2) The user writes numbers on the lids of the Petri dishes according to the test list or writes numbers previously written on the Petri dishes into the test list. (3) The user prepares the culture medium according to the dilution factor specified in the test list. If the dilution factor is not listed in the test list, the user enters a current dilution factor in the test list. (4) The user adds (mixes) a sample to the culture medium of each Petri dish. The user writes the sample name in a comment field on the test list. (5) The user places the Petri dishes into a culture vessel. (6) After a specified time has elapsed, the user removes the Petri dishes from the culture vessel and counts the number of colonies. The user marks the position of a colony with an oil-based pen, for example, while looking through the colony from the bottom of the Petri dish. The number of colonies is recorded in the test list. Note that the user can count the number of colonies for each bacterial species while visually confirming the bacterial species. In this case, the user records the number of colonies for each bacterial species in the test list for each Petri dish. (7) The user activates the PC and reads and enters the numerical values and characters entered in the test list into the spreadsheet software. The number of colonies is aggregated using a macro function of the spreadsheet software or similar.

[0017] Thus, the test list is created manually in the conventional testing procedure, which is extremely tedious for the user. Furthermore, there is a possibility that the aggregation result may also be inaccurate if an error occurs when transferring the numerical values or similar values written in the test list to a spreadsheet. Even if the colony count can be automatically recorded by a colony counter, the possibility of typos and misentry still exists, since the entire test list creation, the entry of the colony count into the test list, and the transfer from the test list to the spreadsheet are all done by hand in the conventional technique.

[0018] Therefore, in this example, it is proposed that an electronic test list be created by PC 1b, the colonies be counted according to an electronic test list, a count result be entered directly into the electronic test list, and the entered numbers are aggregated. This can reduce the user's workload in post-processing the colony count results. Furthermore, incorrect entries can be reduced and test accuracy improved by reducing handwritten or manual input by the user. [Creating a test list (counting table)]

[0019] Fig. 4 shows a UI 50 of a counting application program displayed on the display device 37 of the PC 1b. The counting application program is stored in the storage device 35 and executed by the MCU 30. The UI 50 includes a button, a link, a tab, and the like for switching a variety of functions included in the counting application program.

[0020] The user interface 50 includes a table creation area 51 and a DB display area 61. DB is an abbreviation for database. The table creation area 51 displays at least the count table 55. A title display area 52 receives and displays an input of a title (name) for the count table 55 from the keyboard 32. A button 53 is a button for toggling the execution / non-execution of counting for each cell. A button 54 is a button for instructing the addition of a column to the count table 55. The averaging setting section 56 includes a check box for specifying whether or not to perform averaging of the count results and a selection section for the number of count values to be averaged (= the number of counting iterations).

[0021] The DB display area 61 displays a list of templates (for example, the sample DB 40) of pre-registered counting positions. The counting position corresponds to a row in the counting table 55. The counting position is typically indicated by a name (sample name) of a counting target object. A display 62 displays a name (sample name) of a pre-registered template. An indicator 63 is an object that visually displays a classification label associated with the sample name. The indicator is a label indicating a classification specified by the user (for example, staple food, side dish, or dessert). The indicator 63 can represent a difference in the classification label, for example, by a color difference. The indicator 63 can represent a difference in the classification label by a difference in the shape of the indicator 63.A button 67 is a button for expanding and displaying one or more sub-items that have a parent-child relationship with respect to a specific sample name. The parent-child relationship refers to a relationship between a sample and a plurality of ingredients that comprise the sample. For example, if a sandwich is used as the parent item, the ingredients (for example, ham, lettuce, and egg) that comprise the sandwich are child items. A button 64 is used to add a corresponding template to the counting table 55. Since the sample DB 40 is prepared in advance in this way, the user can easily create the counting table 55.

[0022] In a Fig. In the case shown in Figure 4, when the user presses the key 64 assigned to a sandwich, the MCU 30 adds a row to the count table 55, displays "1" as the ID in an ID display cell of the added row, and displays "Sandwich" in a cell displaying a sample name in the added row. The ID is an abbreviation for identification information. That is, the ID and sample name are set row by row and are "settings for the row." Furthermore, the MCU 30 reads a test condition of the sandwich registered in the sample DB 40 from the storage device 35, adds a new column to the count table 55, and displays the read test condition in the new column. In this example, the test condition includes a bacterial species (for example, generally viable bacteria or Escherichia coli), a dilution factor of a culture medium, a cultivation time of a sample, and the like.For example, each column contains a cell for a bacterial species, a cell for a dilution factor, a cell for a culture time, and a cell for a count. This means that the bacterial species, dilution factor, and culture time are set column by column and are "column settings." In this example, nothing is entered in the count cell because no test has been performed and the count has not yet been determined. The first checkpoint for the sandwich is to use a culture medium with a dilution factor of 100 for generally viable bacteria and apply a culture time of 48 hours. The second checkpoint for the sandwich is to use a culture medium with a 1000-fold dilution factor for generally viable bacteria and apply a culture time of 48 hours.In this way, the MCU 30 adds columns according to the number of test items.

[0023] In Fig. 5, when the user presses the button 64 associated with the kimchi, the MCU 30 reads a test condition of the kimchi registered in the sample DB 40 from the storage device 35 and adds a row and a column corresponding to the read test condition to the count table 55.

[0024] In this example, the kimchi has two check items. The first check item for the kimchi is that a culture medium with a dilution factor of 100 for generally viable bacteria is used and a cultivation time of 48 hours is applied. This also applies to the first check item for the sandwich. Therefore, the MCU 30 discards the first check item, which is included in a template for the kimchi, and does not add it as a new column. The second check item for the kimchi is that a culture medium with a dilution factor of 100 for Escherichia coli is used and a cultivation time of 24 hours is applied. The MCU 30 adds this as a new column in the count table 55.

[0025] Please note that no Escherichia coli test is performed for the sandwich. Therefore, characters or an image indicating "No Test" may appear in the count cell. Similarly, no test is performed for kimchi using a culture medium with a dilution factor of 1000 for generally viable bacteria. Therefore, characters or an image indicating "No Test" may appear in the count cell.

[0026] Note that the execution / non-execution of a count can also be performed by operating a count reverse button 53. When the count reverse button 53 is operated in a state where the cell corresponding to Escherichia coli is selected, the MCU 30 may be able to switch between displaying the characters or image indicating "No Test" and leaving a blank space for inputting a count result.

[0027] As in the Fig. As shown, a search field 65 and a tag search restriction button 66 may be added. As the number of templates registered in the sample DB 40 increases, it becomes difficult for the DB display area 61 to display all the templates at once. Therefore, the MCU 30 may search the storage device 35 based on the characters input into the search field 65 to extract a template and display a search result in the DB display area 61. When the tag search restriction button 66 is pressed, the MCU 30 may display only a sample product filtered by an assigned classification tag. For example, a plurality of product samples may be assigned the same classification tag. In this case, the count table 55 is expanded to include a plurality of sample products assigned the selected classification tag.

[0028] Fig. Figure 6 illustrates the user interface 50 in a case where a counting table is being recreated. For example, the MCU 30 can launch a spreadsheet program in parallel with the application program 39.

[0029] Fig. Figure 7 illustrates a sheet 70 of the spreadsheet software. The MCU 30 receives a copy and paste command to the user interface 50 for the sheet 70 or a cell group selected in the spreadsheet software. As a result, the MCU 30 can Fig. Create counting table 55 shown in Figure 5.

[0030] Fig. 8 illustrates a dialog 90 for adding a column. When the button 54 provided on the user interface 50 is pressed, the MCU 30 displays the dialog 90 on the display device 37. The setting section 91 receives an input of a bacterial species name, which is an element name of a column. A column type setting section 92 receives the setting of whether or not the column type is a count column or a free column. The count column is a column including a cell into which a count value is input. The free column is a column into which the user can freely enter text, an image, and other information such as a remark or a comment. A dilution factor setting section 93 receives the input of a dilution factor. A cultivation time setting section 94 receives the input of a cultivation time.An algorithm setting section 95 receives the image processing settings to be applied to a test image. Residue removal is a mode in which residues (e.g., dirt, stains, and handwriting) adhering to the Petri dish 15 or the like are reduced by image processing. A rapid mode is a mode that emphasizes rapid result confirmation and tests the Petri dish 15 cultured in a shorter culture time than in the related art with higher sensitivity. A culture type setting section 96 is for selecting a culture type (e.g., general viable bacteria (white) or general viable bacteria (black)), and the like.Note that when a list button 96a is pressed, the MCU 30 can read the culture medium candidates from the storage device 35 to create a list and display the list on the display device 37. A setting section 97 receives a setting of a shooting condition (e.g., exposure time) of the main camera 11, an illumination type (e.g., brightness and illumination device), an imaging condition type, an image processing type, and the like. That is, the bacterial species, dilution factor, cultivation time, algorithm setting, culture medium type, or counting setting present in the dialog box 90 are set as default settings for each column. [Counting processing]

[0031] Fig. 9 shows a user interface 100 displayed on the display 37 of the PC 1b during the execution of counting processing by controlling the head device 1a from the PC 1b. A counting table area 101 is an area for displaying the counting table 55 edited via the user interface 50. The result area 102 is an area for displaying a test image 103 captured by the main camera 11 of the head device 1a. Note that the test image 103 may be a moving image or a still image. Generally, the MCU 30 captures a moving image through the main camera 11 and displays the moving image in the result area 102 when executing the setting of the exposure time of the main camera 11, the brightness of each of the ring illuminators 12 and 13 and the coaxial illuminator 14, the selection of the light-emitting elements to be turned on, the selection of image processing, and the like.On the other hand, the MCU 30 captures a still image through the main camera 11 and displays the captured still image in the result area 102 when the counting processing is executed.

[0032] A checkbox 106 is a control object for selecting whether or not to display a count result in the count value area 104. A first software key 105a is a key that has the same function as the first hardware key 8a. A second software key 105b is a key that has the same function as the second hardware key 8b. In this example, a recording instruction (record button) is assigned to the first software key 105a. A registration instruction (registration button) is assigned to the second software key 105b. Fig. 9, the second software key 105b is marked by a dashed line, which means that it is not functional.

[0033] A user clicks and selects a cell corresponding to the Petri dish 15 placed on the table 5 from a plurality of cells contained in a count table displayed in the count table area 101 with the pointer 57. As shown in Fig. As shown in Figure 9, the cell selected with the pointer 57 can be displayed in a highlighted manner so that each cell selected by the user can be recognized. Each cell is stored in the storage device 35 in association with a test condition (colony binarization sensitivity, type of illumination device, brightness, and the like) in advance. The MCU 30 reads the test condition associated with the selected cell from the storage device 35 and transmits the test condition to the head device 1a. The MCU 20 of the head device 1a controls the main camera 11, the ring illumination devices 12 and 13, and the coaxial illumination device 14 according to the received test condition, captures an image, and transmits the image to the PC 1b.When another cell is selected, the MCU 30 reads a test condition associated with the selected cell from the storage device 35 and transmits the test condition to the head device 1a. The MCU 20 of the head device 1a controls the main camera 11, the ring illuminators 12 and 13, and the coaxial illuminator 14 according to the received test condition, captures an image, and transmits the image to the PC 1b. In this way, the user can change the test condition by selecting the cell.

[0034] Fig. Figure 10 shows the user interface 100 displayed on the display device 37 by the MCU 30 when the first software key 105a or the first hardware key 8a, which is the record key, is pressed. The image 103 (still image) of the Petri dish 15 is displayed in the results area 102. The MCU 30 maps the first software key 105a from the record key to a key (count key) for instructing a count.

[0035] Fig. 11 shows the user interface 100 displayed by the MCU 30 on the display device 37 when the first software button 105a or the first hardware button 8a, which is the count button, is pressed. When the count button is pressed, the MCU 30 instructs the head device 1a to count the colonies. The MCU 20 of the head device 1a counts the colonies in response to a count command and transmits a count value to the PC 1b. Note that the counting processing can be performed by the MCU 30. The MCU 30 displays the count value in the count value area 104. At this time, the MCU 30 can convert the count value into CFU / mL (number of colonies per section volume (milliliters)) and display CFU / mL in the count value area 104. For example, each time the count area 104 is clicked with the pointer 57, the MCU 30 can switch the display in the order of count only, CFU / mL only, and count + CFU / mL.Note that CFU is an abbreviation for "colony forming unit." When the count value is acquired, the MCU 30 reassigns the first software button 105a from the count button to the capture button. Furthermore, the MCU 30 changes the second software button 105b and the second hardware button 8b, which are assigned to the capture button, from a non-functional state to a functional state.

[0036] Fig. 12 shows a state in which the register key is pressed. The MCU 30 can write a count value to a currently selected cell and set the next cell to a selection state (cell of interest). In this example, the cell of interest (active cell) is changed from the first row cell to the second row cell. In this way, the MCU 30 automatically selects the next cell, reducing the burden on the user. Note that the MCU 30 returns the second software key 105b and the second hardware key 8b associated with the register key from the ready state to the inoperative state.

[0037] The Fig. The user interface 100 shown in Figure 12 includes a menu 109 for changing the target of the cell display. Fig. 12 is displayed in a cell “100” because “Counting number” is selected in the change menu 109.

[0038] Fig. 13 shows the user interface 100 displayed by the MCU 30 on the display device 37 when a cell into which an input value has been entered is double-clicked. A setting screen 120 includes a control object for setting a parameter related to a colony detection algorithm from a test condition associated with the cell selected by the double-click. For example, a slider bar 121 is a control object for setting a threshold for removing small particles through image processing. A slider bar 122 is a control object for adjusting the colony detection sensitivity.

[0039] The MCU 30 can display a marker, such as a circle, superimposed on a portion detected as a colony in the image 103 displayed in the result area 102. Since the MCU 30 changes an algorithm according to the setting of each of the slide bars 121 and 122, the positions and number of markers indicating the colonies also change. This allows the user to easily find a suitable setting value. [Flowchart](1) Main processing of PC 1b

[0040] Fig. 14 is a flowchart showing a series of processing executed by the MCU 30 of the PC 1b. The MCU 30 executes the following processing according to the counting application program stored in the storage device 35.

[0041] In S1, the MCU 30 executes the processing of a count table. As described with reference to Fig. 4 to 8 and the like, the count table is edited or created via the user interface 50 and the like.

[0042] In S2, the MCU 30 stores the count table in the storage device 35.

[0043] In S3, the MCU 30 identifies the counting table. The counting table can be identified using the front camera 10 and the test list or a user authentication tag, or it can be identified using a file dialog.

[0044] In S4, the MCU 30 reads the identified count table from the storage device 35. Then, the Fig. 9 is displayed on the display device 37.

[0045] In S5, the MCU 30 identifies a cell into which a count value is to be written. First, a cell in the top row of the count table can be selected, or a cell can be selected by clicking on it with the pointer 57.

[0046] In S6, the MCU 30 identifies a test condition associated with the active cell. For example, the MCU 30 reads the test condition associated with each cell from the storage device 35 once the count table has been created.

[0047] In S7, the MCU 30 sets the test condition associated with the active cell in the head device 1a. As described above, the sensitivity of the main camera 11, an illumination device to be turned on, the brightness, the number of light-emitting elements to be turned on (irradiation direction), the image processing (HDR or ring distance), a counting algorithm (a parameter such as a threshold), and the like are transmitted to the head device 1a.

[0048] In S8, the MCU 30 determines whether the test condition has been changed. As described above, the test condition associated with the cell can be changed at any time, even during a test. Therefore, if the test condition is changed, the MCU 30 returns to S7 and transmits the changed test condition to the head device 1a. If the test condition is not changed, the MCU 30 proceeds to S9.

[0049] In S9, the MCU 30 determines whether a recording instruction has been entered by a user. The user can issue the recording instruction by pressing the first hardware button 8a of the head device 1a or the first software button 105a of the user interface 100. If the recording instruction is not entered, the MCU 30 returns from S9 to S8. If the recording instruction is entered, the MCU 30 proceeds from S9 to S10.

[0050] In S10, the MCU 30 transmits a mapping instruction to the head device 1a.

[0051] In S11, the MCU 30 captures an image (test image) of the Petri dish image 103 captured by the main camera 11 of the head device 1a and displays the test image in the result area 102 of the user interface 100.

[0052] In S12, the MCU 30 determines whether a counting instruction is present or not. The user can input the counting instruction by pressing the first hardware button 8a of the head device 1a or the first software button 105a of the user interface 100 assigned as a counting button. If the counting instruction is not input, the MCU 30 returns from S12 to S8. If the counting instruction is input, the MCU 30 proceeds from S12 to S13.

[0053] In S13, the MCU 30 transmits the counting instruction to the head device 1a. Note that when the counting processing is performed by the PC 1b, the MCU 30 performs the counting processing instead of the MCU 20.

[0054] In S14, the MCU 30 receives a count result from the head device 1a and displays the count result in the count value area 104. Note that in a case where the MCU 30 executes the count processing in S14, the MCU 30 displays the count result obtained by executing the count processing in the count value area 104.

[0055] In S15, the MCU 30 determines whether the test condition, such as image processing and counting algorithm, has been changed. If the test condition is changed, the MCU 30 returns to S13. If the test condition is not changed, the MCU 30 proceeds to S16. Note that the change in the test condition in S8 is assumed to be a change in the test condition that requires re-capturing an image. The change in the test condition in S15 causes a change in the image processing of the captured image, but it is assumed that re-capturing an image is not required.

[0056] In S16, the MCU 30 determines whether or not a registration instruction has been entered by the user. The user can enter the registration instruction by pressing the second hardware button 8b of the head device 1a or the second software button 105b of the user interface 100 assigned as a registration button. If the registration instruction has not been entered, the MCU 30 returns from S16 to S8 to perform a new recording or change the test conditions. If the registration instruction is entered, the MCU 30 proceeds from S16 to S17.

[0057] In S17, the MCU 30 registers the counting result in the active cell.

[0058] In S18, the MCU 30 determines whether all counts are complete. For example, if the count results have been entered into all cells in the count table, the MCU 30 determines that the counts are complete. If there is still a cell without an input, the MCU 30 proceeds from S18 to S5 and changes the active cell to the next cell (cell identification). (3) Registration of the sample database

[0059] A count table has multiple rows and columns, and each cell is associated with a test condition. The count table and a test list can be newly created for each day. However, there is also the case where a test is performed every day for the same sample. Therefore, the overhead of creating the count table is reduced if a count table for a sample with a high test frequency is registered in the Sample DB 40 in advance. Therefore, once a sample table has been created, the user can register a row item corresponding to each sample in the Sample DB 40.

[0060] Fig. Fig. 15 is a flowchart showing the processing of the sample DB 40 by the MCU 30 of the PC 1b. The MCU 30 executes the following processing according to the application program 39 stored in the storage device 35.

[0061] In S41, the MCU 30 receives the selection of a row element to be entered into the sample DB 40 from among a plurality of row elements included in the count table. For example, the MCU 30 may receive a click of the pointer 57 on any row element among the row elements included in the sample table.

[0062] In S42, the MCU 30 receives an addition instruction for the selected row element. The addition instruction can be input, for example, when a right-click is performed by the pointer 57 in a state where the row element has been selected.

[0063] In S43, the MCU 30 acquires a sample name of the row item to be added and determines whether the same sample name already exists in the sample DB 40 (duplicate determination). If the row item to be added does not yet exist, the MCU 30 proceeds to S43 through S45. If the row item to be added exists in the sample DB 40, the MCU 30 proceeds from S43 to S44.

[0064] In S44, the MCU 30 asks the user whether or not to overwrite the row element in the sample DB 40. If a delete instruction is entered, the MCU 30 cancels the addition of the row element. If an overwrite instruction is entered, the MCU 30 proceeds from S44 to S45.

[0065] In S45, the MCU 30 acquires an element name (e.g., a sample name, a bacterial species, a culture medium type, or a dilution factor) that constitutes the row element to be added.

[0066] In S46, the MCU 30 receives from the memory device 35 a test condition associated with a cell of the row element.

[0067] In S47, the MCU 30 registers the sample name and test conditions in the sample DB 40.

[0068] In S48, the MCU 30 updates the display of the sample DB 40 in the user interface 50. (6) Counting colonies

[0069] Fig. Figure 16 shows the colony counting processing executed by the MCU 20 of the head device 1a according to the control program. However, the image processing and counting processing may also be executed by the MCU 30.

[0070] In S81, the MCU 20 acquires a counting algorithm from a test condition received from the PC 1b. Specifically, the image processing and a threshold parameter (e.g., a binarization threshold) used in the counting algorithm are acquired.

[0071] In S82, the MCU 20 applies the counting algorithm to a test image captured by the main camera 11. For example, image processing such as HDR or ring removal is applied to the test image.

[0072] In S83, the MCU 20 counts the colonies contained in the test image according to the test condition (threshold parameter). <Zweite Ausführungsform>

[0073] Meanwhile, among users, there is a user who creates a test list and a counting table using a spreadsheet program (the spreadsheet program 41) that is widely used. There is a case where such a user needs to introduce the colony counter 1 and transition to an environment in which a test list and a counting table are created by the application program 39. In this case, the user sometimes wishes to redirect the test list and the counting table created by the widely used spreadsheet software as assets. Alternatively, it is sometimes desired to create a test list and a counting table, or a configuration file serving as a source thereof, sequentially using the widely used spreadsheet software.

[0074] Therefore, in the second embodiment, a function for converting a user file (configuration file) created by a widely used spreadsheet software into a test list and a count table is proposed. (1) Procedure (i) A user creates a test list using the spreadsheet software in use. If the test list already exists, this step is skipped. The format of an electronic file of the test list can be CSV format, Excel format (registered trademark) of Microsoft Corporation, or another format. (ii) The user redirects the test list using the spreadsheet software to create a configuration file on a list to be read by the colony counter 1. For example, the user adds a cell to the test list using the spreadsheet software and describes the tag information in the added cell. The user saves the test list, in which the tag information is embedded, as a spreadsheet software configuration file. (iii) The PC 1b performs the colony counting according to the configuration file or by converting the configuration file into a counting table for the colony counter 1. (2) User file created by the spreadsheet software (2-1) Business file (count table also serves as test list)

[0075] Fig. Figure 17 shows the business file 200 created by the user using the spreadsheet program 41. The business file 200 is used as a counting table, which also serves as a test list or simply a counting table. The names of the samples (sample names) are described in the leftmost column. The second column describes the preparation date and time of each of the samples. The third column describes that a white culture medium for general viable bacteria is used and the dilution factor is 1:10. The fourth column describes that the white culture medium for general viable bacteria is used and the dilution factor is 1:100. The fifth column describes that the white culture medium for general viable bacteria is used and the dilution factor is 1:1000.The sixth column describes that a dark culture medium is used for the Escherichia coli group, and the dilution factor is 1:10. The seventh column describes that the dilution factor for Staphylococcus aureus is 1:10. The eighth column contains batch information, which indicates a manufacturing lot. The ninth column provides a comment.

[0076] The user generally prints such a business file 200 on paper using a printer and uses the business file 200 as a counting table, which also serves as a test list. (2-2) User file (configuration file), created with a spreadsheet program

[0077] Fig. Figure 18 shows the configuration file 210 created by the user using the spreadsheet program 41. The configuration file 210 is created by the user inserting a marker and a character string into the business file 200 using the spreadsheet program 41. For example, the user can create the configuration file 210 by copying and renaming the business file 200. In this case, both the business file 200 and the configuration file 210 are maintained in the storage device 35.

[0078] A [START] tag is a tag that defines a starting position of columns (column elements) and rows (row elements) required to create the counting table 55 in the configuration file 210. The starting position is expressed as the coordinates of a cell and can be expressed, for example, as (START COLUMN, START ROW). An tag is a tag that defines an ending position of the columns and rows required to create the counting table 55 in the configuration file 210. The ending position is expressed as the coordinates of a cell and can be specified, for example, as (END COLUMN, END ROW).

[0079] A [DATE] tag displays a column describing date and time information, such as the date and time of manufacture. A [COUNT] tag displays a column containing a counting cell, into which a colony count is entered. Note that two cells corresponding to the fourth and fifth columns from the left in the first row from the top in Fig. 18 are empty. This is an abbreviated description that should follow a cell highlight to the left of the corresponding cell. This means that the fourth and fifth columns are also columns, each containing the count cell according to the [COUNT] tag. A [COMMENT] tag indicates a column in which the user can freely enter a string.

[0080] A [MEDIA TYPE] tag indicates the type of culture medium and the name of a test setting. The test setting information indicates various parameters (for example, an acquisition condition and an image processing condition) set in the colony counter 1. A [FAVORITE] tag indicates the name of a test setting that the user has registered in advance as a favorite from a variety of test settings. A [NAME] tag indicates the name of a column (for example, the name of bacteria) displayed in the counting table 55. An [EARLY] tag indicates whether or not a rapid mode is valid. Rapid mode is a mode in which counting is performed at a time when a legally specified cultivation time ends and at an intermediate time before the end time.Rapid mode has the advantage of allowing a sample to be discarded and reproduced midway through a long culture period. A [DILUTION] tag indicates the dilution factor. An [ON] tag indicates that counting must be performed using a standard assay setting or indicates the validity of Rapid mode. Fig. For example, Figure 18 shows the [ON] mark in a row of the sandwich set. This means that a test setting with a name specified by the [MEDIUMTYPE] tag ("General Viable Bacteria [Background: white]") must be applied to a count cell. It is assumed that "General Viable Bacteria [Background: white]" is associated with "General Viable Bacteria / Setting 1." In the third column, "General Viable Bacteria / Setting 2," a test setting name, is entered as a string for Rice Omelette instead of the [ON] tag. This indicates that "General Viable Bacteria / Setting 2" must be applied instead of "General Viable Bacteria [Background: white]" (i.e., General Viable Bacteria / Setting 1, which is the default test setting).

[0081] There is no description in a column with a dilution factor of 1:100 for rice omelet. This suggests that counting is not performed at a dilution factor of 1:100 for rice omelet.

[0082] As in Fig. As shown in Figure 18, when a colony count is performed for a plurality of cultivation conditions or bacterial species for one sample name, the [COUNT] tag is described in each of the corresponding columns.

[0083] Fig. 19 is a view showing cell groups in the configuration file 210.

[0084] A cell group CG1 comprises one or a plurality of cells in which identification information (sample name) of a test body is described.

[0085] A cell group CG2 comprises one cell in which the [DILUTION] tag is described and one or more cells in which an actual dilution factor is described. Cell group CG2 can also include cell groups CG4 and CG5, as the cultivation conditions are maintained.

[0086] A cell group CG3 comprises cells corresponding to the respective counting cells of the counting table 55. In each of the cells of the cell group CG3, the [ON] tag indicating that a count must be performed with a standard test setting, an arbitrary character string indicating that a count must be performed with a test setting identified by the described character string, a space (null character) indicating that a count is not performed, or the like is described.

[0087] Cell group CG4 includes a cell describing the [MEDIUMTYPE] tag and a cell containing a string specifying the name of the default test setting. An empty cell in cell group CG4 indicates that a test setting in a cell to its right is valid.

[0088] Cell group CG5 includes a cell containing the [FAVORITES] tag and a cell containing a string specifying the name of a preferred test setting. An empty cell in cell group CG5 indicates that the default test setting assigned by the [MEDIUMTYPE] tag is valid. (3) Counting table

[0089] Fig. Figure 20 illustrates that the counting table 55, which was created by converting or analyzing the configuration file 210, is displayed in the counting table area 101. If one Fig. 18 shown configuration file 210 with the in Fig. 20, it can be understood that a positional relationship between the cells of the two is generally maintained. Note that the MCU 30 stores and maintains a relationship between a cell in the configuration file 210 and a corresponding cell in the count table 55 in the storage device 35. Further, a test setting is associated with a count cell 224 in the count table 55. The MCU 30 identifies a test setting based on tag information of a cell in the configuration file 210 and associates the identified test setting with the corresponding count cell 224.

[0090] If the Fig. 18 shown configuration file 210 with the in Fig. 20, the MCU 30 copies a sample name described in cell group CG1 of the configuration file 210 into a sample name column in the count table 55. The MCU 30 also copies the manufacturing date and time described in a cell assigned by the [DATE] tag in the configuration file 210 into a manufacturing date and time column in the count table 55.

[0091] The MCU 30 also copies a dilution factor described in the cell group CG2, which is identified by the tag [DILUTION], into a row of a dilution factor in the count table 55. Furthermore, the MCU 30 also copies a column name, which is assigned by the [NAME] tag, into a row with a column name in the count table 55.

[0092] Note that the MCU 30 divides a column in which the fast mode is enabled by the [EARLY] tag and the [ON] tag into two columns. A first column 227 stores a count result of the first time point (for example, a time point of 24 hours). A second column 228 stores a count result of the second time point (for example, a time point of 48 hours).

[0093] The MCU 30 provides the counting cell 224 and a counting cell 226 in the counting table 55 so that they correspond to the respective cells of the cell group CG3 in the configuration file 210. The MCU 30 can display an icon 225 for confirming or editing the test setting assigned to the counting cell 224 in the counting cell 224 in which a count is to be performed. For example, the icon 225 is clicked with the pointer 57. The MCU 30 grays out the counting cell 226 in which no count is to be performed.

[0094] In this way, in the second embodiment, the business file 200 and the configuration file 210 can be created using the spreadsheet program 41 normally used by the user. Furthermore, the MCU 30 can convert the configuration file 210 into the counting table 55 for the colony counter 1 according to a conversion or import function installed in the application program 39. This reduces the workload for creating the counting table 55. (4) Another example of a counting table

[0095] Fig. 21 shows another example of the counting table 55 created from the configuration file 210. In the Fig. In the counting table 55 shown in Figure 20, the plurality of counting cells 224 and 226 are arranged in one row for one sample name. However, this is only an example. As shown in Fig. As shown in Figure 21, a row can be created for each combination of sample name and dilution factor, in which a counting result is entered. Fig. 21, the number of rows in which counting results are entered is also three. Thus, an arrangement of cells in the configuration file 210 and an arrangement of cells in the counting table 55 do not necessarily match. (5) Reflection of the counting result from the counting table into the configuration file

[0096] Fig. 22 illustrates a procedure of mirroring count results input to the count cells 224a, 224b, and 224c of the count table 55 into the configuration file 210 and the business file 200 by the colony counting device 1. The MCU 30 stores in the storage device 35 a relationship between the count cells 224a, 224b, and 224c of the count table 55, the cells 237a, 237b, and 237c corresponding thereto in the configuration file 210, and the cells 238a, 238b, and 238c corresponding thereto in the business file 200. For example, the storage device 35 stores information about the relationship between the cells, indicating that the count cell 224a, the cell 237a, and the cell 238a are related to each other and form a cell group.Similarly, the storage device 35 stores information about the relationship between the cells, indicating that the counting cell 224b, the cell 237b, and the cell 238b are related to each other and form a cell group. Furthermore, the storage device 35 also contains information about the cell-to-cell relationship, indicating that the counting cell 224c, the cell 237c, and the cell 238c are related to each other and form a cell group. The MCU 30 forwards the counting results from the counting table 55 to the configuration file 210 and the business file 200, referring to this relationship. That is, the counting results input into counting cells 224a, 224b, and 224c are mirrored into cells 237a, 237b, and 237c, respectively, and into cells 238a, 238b, and 238c. It has been described that the counting result is mirrored into configuration file 210, which serves as an example here. However, this is only an example.The MCU 30 can output the counting result as a new file in a format corresponding to a data structure existing in an application.

[0097] Meanwhile, both the configuration file 210 and the business file 200 are created using the spreadsheet program 41. The spreadsheet program 41, such as Excel (registered trademark) of Microsoft Corporation, has a cell reference function. For example, the reference to cell 237a of the configuration file 210 can be described in cell 238a of the business file 200 (for example, = [ConfigurationFile.xlsx] WorksheetName! CellCoordinates). Consequently, the count result copied from the counting table 55 to the configuration file 210 can be further input into the business file 200. (6) Allow empty row (empty cell)

[0098] Fig. Figure 23 illustrates the conversion of configuration file 210, in which an empty cell with the sample name exists in cell group CG1, to count table 55. Users sometimes copy the configuration file 210 created in the past to create a new configuration file 210. Typically, the number of samples as test targets is often constant, but there is a case where some samples are missing and excluded from the test targets. In this case, it would be convenient for users if the missing samples could be easily excluded from the test targets.

[0099] As in Fig. Therefore, as shown in Figure 23, the user deletes a sample name that has been excluded from the test targets to obtain an empty cell. At this time, the contents of cells with test labels, such as cell group CG3, are not necessarily deleted. The MCU 30 analyzes the configuration file 210, ignores any test label cells that exist in the same row (blank row) as a blank cell if the blank cell is found in cell group CG1, and creates the count table 55.

[0100] As in Fig. As shown in Figure 23, a counting row (a row including a counting cell) corresponding to the same empty row as the empty cell in the cell group CG1 in the configuration file 210 is not provided in the counting table 55. As a result, in the counting table 55, a counting row of Salad Bowl is arranged after a counting row of Sandwich Set, and a counting row of Omelette Sandwich is arranged below a counting row of Rice Omelette.

[0101] In this way, the MCU 30 creates the counting table 55, ignoring the empty cell according to a conversion function of the application program 39. This makes it possible to easily exclude some samples that are missing from the test targets, which is convenient for the user.

[0102] Note that strings in test label cells are simply ignored, even if they remain. This is useful when resuming production of some missing samples. It is possible to restore a test setting for a sample name (enable the test label cell strings) by rewriting the sample name to the empty cell. (7) Subdivision of the Petri dish

[0103] The user sometimes uses a Petri dish divided into multiple compartments by a partition. This is convenient for obtaining multiple counting results that have different cultivation conditions (e.g., dilution factors) for the same sample.

[0104] Fig. 24 shows the Petri dish 15 divided by partitions into M (for example, M = 4) effective areas 231 to 234. In this case, the MCU 30 needs to divide an effective area to be counted in an image of the Petri dish 15 into M effective areas and perform a count for each of the M effective areas. It is complicated and troublesome for the user to make settings to cause the colony counting device 1 to perform the above.

[0105] Fig. 25 illustrates a method for assigning a customized test setting for each sample. In this example, character strings "Upper Left Detection," "Lower Left Detection," "Upper Right Detection," and "Lower Right Detection" indicating names of test settings registered in advance as favorites are described in cell group CG3. The MCU 30 searches the configuration file 210 and assigns the name of a test setting to the corresponding counting cell 224 in the counting table 55 when it finds a test setting cell in cell group CG3 that includes the character string indicating the name of the test setting. When the icon 225 displayed in the counting cell 224 is pressed by the user, the MCU 30 reads the test setting from the storage device 35 based on the name of the test setting assigned to the counting cell 224, applies the test setting to the colony counter 1, and performs a count.The user can also easily create the counting table 55 for a test using the Petri dish 15 divided into the four effective areas 231 to 234 by creating the test settings named “top left detection,” “bottom left detection,” “top right detection,” and “bottom right detection” in advance.

[0106] In this way, any character string for designating a test setting name can be described in a test name cell in cell group CG3. This means that the user can directly describe test setting names in the respective test name cells without being limited to the divided Petri dish 15.For example, the user can pre-store a variety of test settings with different combinations of binarization sensitivity, small particle removal threshold, shape separation degree, lint removal degree, sample information (e.g., a type of culture medium, a Petri dish diameter, a bacteria name, and a sample solution amount), and record settings (e.g., an illumination setting, a brightness setting, anti-glare activation / deactivation, resolution enhancement activation / deactivation, and the like) in the storage device 35, and describe the names of these test settings in the test name cells. This allows the test setting to be linked to the count cell 224. (8) Reference to sample DB

[0107] There is a case where the user wants to constantly associate the same test setting with samples of the same name. If the user remembers the name of a specific test setting, as described above, it is sufficient to describe the name in a cell with a test label. However, it may be difficult to remember the names of all test settings. Meanwhile, the test settings are linked to sample names in the sample DB 40. Therefore, it would be convenient for the user if the test setting stored in the sample DB 40 for each sample name could be linked to the counting cell 224 via the configuration file 210.

[0108] Fig. 26 is a view showing a [SAMPLE DB] tag. The [SAMPLE DB] tag is a tag that can be written to a test name cell. When the [SAMPLE DB] tag is found during scanning of the configuration file 210, the MCU 30 refers to the Sample DB 40 based on a sample name that exists in a row where the [SAMPLE DB] tag is present, and associates (a name of) a test setting associated with the sample name with the test name cell in which the [SAMPLE DB] tag is written. More specifically, the MCU 30 links the test setting stored in the Sample DB 40 with the count cell 224 of the count table 55 associated with the test name cell. Consequently, the test setting can be assigned to the count cell 224 even if the user does not remember the name of the specific test setting associated with the sample name. (9) Date and time of manufacture and batch number

[0109] As in Fig. 18 and the like, the [COMMENT] tag is prepared in the second embodiment. The reason for this will be described below.

[0110] There is a case where the user wants to distinguish multiple samples with the same sample name based on the preparation date, preparation time, and batch number. For example, the user can summarize a context (such as the preparation date and time and a batch number) when conducting a series of tests in a "Comment" column in the counting table 55. Generally, it is necessary to enter information into the comment column for each Petri dish. Therefore, it is not easy to efficiently enter the context information managed by the user into the comment column.

[0111] Therefore, in the second embodiment, it is possible to add column information corresponding to the context to the configuration file 210. In this way, the addition of data of a user-desired type for each sample is implemented.

[0112] For the manufacturing date and time, the [DATE] tag is prepared for a date and time attribute. The [DATE] tag means that an input character string is treated as date and time information (date and time attribute). The [DATE] tag enables searches using the manufacturing date and time as keys. Furthermore, when a counting result is exported to a spreadsheet file under the control of the spreadsheet program 41, the MCU 30 can assign a time attribute to a column of the manufacturing date and time in the spreadsheet file. This can facilitate data management by the user.

[0113] The [COMMENT] tag is a tag to reach the comment column in the counting table 55. In Fig. 18 and the like, the comment column can be assigned a name "Lot" by further using the [NAME] tag in combination. The MCU 30 can recognize the character string "Lot" as an attribute indicating the batch number or the like.

[0114] As in Fig. 18, by using the [COMMENT] tag and the [DATE] tag, not only the test setting, such as the dilution factor, but also the batch and the preparation date and time of the sample are reflected in the counting table 55 and can be managed by the application program 39. (10) Averaging

[0115] There is a case where it is desired to cultivate fungi on a plurality of Petri dishes 15 to which the same test setting (for example, bacterial species and dilution factor) is applied to the same counting target, obtain counting results in the plurality of Petri dishes 15, and average the plurality of counting results. Therefore, in the second embodiment, a [REPEAT:n] tag is used. When the [REPEAT:n] tag is found during scanning of the configuration file 210, the MCU 30 detects that the same test setting is applied and counting is performed n times, and arranges n counting series to which the same test setting is applied in the counting table 55.

[0116] Fig. Figure 27 shows a counting result (counting table 55) of the configuration file 210 in which the [REPEAT:n] tag is described. In this example, a [REPEAT:2] tag is described, and the MCU 30 detects that a count is performed twice with a default test setting (general viable bacteria [background: white]) for the sample names "rice ball" and "fish roll," and an average of the results is obtained. In the counting table 55, the MCU 30 arranges three counting cells for each of the samples "rice ball" and "fish roll." The first counting cell stores the first counting result. The second counting cell stores the second counting result. The third counting cell stores an average of the first counting result and the second counting result.

[0117] In this way, when the [REPEAT:n] tag is found when scanning the configuration file 210, the MCU 30 arranges the n counting rows for sample names described above a cell with the [REPEAT:n] tag in the cell group CG1 in the counting table 55. In addition, the MCU 30 also arranges a counting row for storing the average value in the counting table 55.

[0118] It should be noted that the MCU 30, as shown in Fig. 27, between a column for storing the sample name and a column for storing the counting result, a column with the number of times can be arranged to indicate names such as the first time, the second time and the average value. (11) Configuration file without tag

[0119] In the configuration file 210 described above, the MCU 30 creates the counting table 55 by reading a flag such as [START], , [COUNT], or [COMMENT] and associating a predetermined test setting with the counting cell 224. However, in the second embodiment, the flag may be omitted.

[0120] Fig. 28 illustrates a method for creating the counting table 55 from the configuration file 210 that does not include a tag. The storage device 35 stores a conversion rule in advance. The conversion rule describes, for example, that a sample name is described in column A, a test setting name in the first row, a fungus name in the third row, a dilution factor in the fifth row, and the like. Further, the conversion rule includes copying the sample name described in column A into a sample name column in the counting table 55, assigning the test setting identified by the name in the first row to a counting cell in the counting table 55, copying a character string described in the third row into a fungus name cell in the counting table 55, and copying a character string described in the fifth row into a dilution factor cell in the counting table 55.

[0121] In this way, the conversion rule includes a rule that specifies to which cell coordinates in the counting table 55 a character string described in a cell with specific coordinates in the configuration file 210 is copied. Furthermore, the conversion rule also includes a rule that specifies that a test setting identified by the character string described in the cell of specific coordinates in the configuration file 210 is associated with the corresponding counting cell 224 in the counting table 55. The MCU 30 scans cells in the configuration file 210 according to the conversion rule, interprets the character string described in the cell of specific coordinates according to the conversion rule, and reflects the character string in the counting table 55.

[0122] Since the conversion rule is stored in advance in the storage device 35 in this way, the MCU 30 can convert the configuration file 210 into the count table 55 without using a tag. Alternatively, it can be said that the user needs to know the conversion rule and then input a character string according to the conversion rule into a predetermined cell in the configuration file 210. (12) Partial adjustment of the test setting

[0123] In Fig. 18, a test setting is assigned by a combination of the [IN] tag and the [MEDIA TYPE] tag, the [FAVORITE] tag, the [SAMPLE DB] tag, or by directly entering a test setting name. However, this is only an example. The contents of a test setting can be directly described in a test label cell. For example, if a standard test setting has J parameters, all J parameters can be described in the test label cell. This means that the standard test setting is essentially unused. Alternatively, K parameters among the J parameters can be described in the test label cell (J > K >= 1). In this case, the standard test setting is applied to the (J - K) parameters among the J parameters, and the test setting described in the test label cell is applied to the K parameters. This means that it is possible to customize part of the standard test setting.

[0124] Fig. Figure 29 shows an example of the configuration file 210 in which the default test setting can be partially or completely customized. In this example, a sensitivity setting and a small particle removal threshold are described directly in test label cells for a sample name "Sausage." That is, only the sensitivity and small particle removal threshold in the test setting named "General Viable Bacteria [Background: White]," assigned by the [MEDIUM TYPE] tag, are adjusted to the values assigned in the test label cells. The acquisition brightness is described directly in the test label cells for the sample name "Frozen Pizza."This means that only the acquisition brightness in the test setting named "General Viable Bacteria [Background: white]", assigned by the [MEDIA TYPE] tag, is adjusted to a value in the test label cells.

[0125] In this way, the default test setting can be partially or completely customized by describing a test parameter directly in the test label cell. (13) Flowchart(13-1) Main flowchart

[0126] Fig. 30 illustrates the processing of converting the configuration file 210 created by the user using the spreadsheet program 41 into the counting table 55 by the application program 39.

[0127] In S91, the MCU 30 reads the configuration file 210 from the storage device 35. The configuration file 210 can be assigned via a user interface, such as a file dialog. Note that the MCU 30 acts as a reading section for the file.

[0128] In step S92, the MCU 30 searches for the [START] tag in the configuration file 210 and sets the coordinates of a cell containing the [START] tag as the starting coordinates of the conversion processing. In this way, the MCU 30 functions as a tag search section and a starting coordinate setting section.

[0129] In step S93, the MCU 30 searches the configuration file 210 for the tag and sets the coordinates of a cell containing the tag as the end coordinates of the conversion processing. In this way, the MCU 30 functions as a tag search section and an end coordinate setting section.

[0130] At S94, the MCU 30 starts scanning from the cell where the [START] tag is written to the right, searching for a cell where any tag is written. Thus, the MCU 30 functions as a cell scanning section and a tag searching section.

[0131] In S95, the MCU 30 acquires a test setting corresponding to the found tag. Here, the test setting is a set of information (for example, a column name and the like) required to set a corresponding column in the count table 55. According to Fig. 18, the [DATE] tag, the [COUNT] tag, and the [COUNT] tag are found. Details of S95 will be explained later with reference to Fig. 31. In this way, the MCU 30 acts as a detection section that detects the test setting of the column.

[0132] In S96, the MCU 30 determines whether a sampling position reaches an end column (a column where the tag is written). If the sampling position is not the end column, the MCU 30 returns to S94, shifts the sampling position one column to the right, and searches for a tag. When the sampling position reaches the end column, the MCU 30 proceeds from S96 to S97. In this way, the MCU 30 functions as a determination section.

[0133] In S97, the MCU 30 starts scanning the lower side of the cell in which the [START] tag is written, and searches for a cell in which a tag or sample name is written.

[0134] In S98, the MCU 30 acquires a test setting for each sample. Details of S98 will be explained later with reference to Fig. 32. In this way, the MCU 30 functions as a test setting acquisition section.

[0135] In S99, the MCU 30 determines whether the scan position has an end row (a row where the tag is written). If the scan position is not the end row, the MCU 30 returns to S97, moves the scan position down one column, and searches for a tag. When the scan position reaches the end column, the MCU 30 proceeds from S96 to S97.

[0136] In S100, when the MCU finds the [REPEAT] tag, the MCU 30 reflects an averaging setting in the count table 55. In this way, the MCU 30 functions as a reflection section for marking or as a reflection section for averaging setting. (13-2) Sub-flowchart

[0137] Fig. Figure 31 illustrates the details of S95.

[0138] In S101, the MCU 30 determines whether the [COUNT] tag is present or not. If the [COUNT] tag is found, the MCU 30 proceeds from S101 to S102. Note that the MCU 30 proceeds to S102 even if a cell to the right of a cell in which the [COUNT] tag is written is an empty cell.

[0139] In S102, the MCU 30 recognizes a column including the cell in which the [COUNT] tag is written as a counting execution column and acquires a test setting (for example, a name of a standard test setting, a column name (a name of a bacterial species), a dilution factor, and other test settings) from the column.

[0140] In S103, the MCU 30 reflects the acquired test setting in the count table 55.

[0141] In S101, if the found tag is not the [COUNT] tag, the MCU 30 proceeds from S101 to S104.

[0142] In S104, the MCU 30 determines whether the found tag is the [DATE] tag or not. If the [DATE] tag is found, the MCU 30 proceeds from S104 to S105.

[0143] In S105, the MCU 30 detects a column containing a cell in which the [DATE] tag is described as a column for managing the manufacturing date and time. Then, the MCU 30 proceeds from S105 to S103 and reflects the manufacturing date and time management column in the count table 55. For example, the manufacturing date and time described in the column are copied to a corresponding column in the count table 55.

[0144] In S104, if the found tag is not the [DATE] tag, the MCU 30 proceeds from S104 to S106.

[0145] In S106, the MCU 30 determines whether the found tag is the [COMMENT] tag or not. If the [COMMENT] tag is found, the MCU 30 proceeds from S106 to S107.

[0146] At S107, the MCU 30 detects a column containing a cell in which the [COMMENT] tag is described as a comment column and acquires a character string (for example, a column name such as "Lot" or "Comment") described in the column. Then, the MCU 30 proceeds from S106 to S103 and returns the comment column to the count table 55. For example, the character string (for example, the column name such as "Lot") obtained from the comment column of the configuration file 210 is copied into a corresponding column of the count table 55. (13-3) Sub-flowchart

[0147] Fig. Figure 32 illustrates the details of S98.

[0148] In S111, the MCU 30 receives a sample name from the configuration file 210. Note that an empty cell is skipped.

[0149] In S112, the MCU 30 determines a column type. If an indicator indicating the column type is the [COUNT] indicator, the MCU 30 proceeds from S112 to S113.

[0150] In S113, the MCU 30 searches for a dilution factor. The dilution factor is determined, for example, from a cell that represents an intersection of the [COUNT] tag or the empty cell and the [DILUTION] tag.

[0151] In S114, the MCU 30 moves down from the dilution factor cell and branches processing according to a cell value. If the cell value is [ON], the MCU 30 proceeds from S114 to S115.

[0152] In S115, the MCU 30 detects a cell in which the [ON] tag is described as a counting cell (test designation cell) and assigns the counting cell to the standard test setting assigned by the [MEDIUMTYPE] tag. As a result, the standard test setting is assigned to the counting cell in the counting table 55 that corresponds to the test designation cell in the configuration file 210. In this way, the MCU 30 functions as a mapping section.

[0153] In S116, it is determined whether the dilution factor search is complete. If there are multiple dilution factors for a sample name, the MCU 30 returns from S116 to S113.

[0154] If the value of the cell is any string in S114, the MCU 30 proceeds to S114 to S119.

[0155] In S119, the MCU 30 recognizes the cell as a test label cell and assigns the count cell 224 corresponding to the test label cell to a test setting identified by the character string described in the test label cell. As a result, the test setting identified by a name in the test label cell in the configuration file 210 is linked to the count cell 224 in the count table 55 corresponding to the test label cell. The MCU 30 then proceeds from S119 to S116.

[0156] When the value of cell [SAMPLE-DB] is in S114, the MCU 30 proceeds from S114 to S120.

[0157] In S120, the MCU 30 recognizes the cell as a test name cell, acquires a test setting associated with the sample name from the sample DB 40, and assigns the count cell 224 corresponding to the test name cell to the acquired test setting. As a result, the test setting acquired from the sample DB 40 based on the sample name is assigned to the count cell 224 in the count table 55 corresponding to the test name cell. The MCU 30 then proceeds from S120 to S116.

[0158] If the value of the cell in S114 is empty, the MCU 30 proceeds from S114 to S121.

[0159] In S121, the MCU 30 detects that the cell is a non-counting cell. For example, the MCU 30 may gray out the non-counting cell 226 in the counting table 55 associated with the empty test label cell. The MCU 30 then proceeds from S121 to S116.

[0160] If it is determined in S112 that the mark indicating the column type is the [DATE] mark, the MCU 30 proceeds to S112 to S117.

[0161] In S117, the MCU 30 captures the value of the cell as date and time information, and copies the date and time information into the corresponding count cell 224 in the count table 55. After that, the MCU 30 proceeds from S117 to S116.

[0162] If it is determined in S112 that the mark indicating the column type is the [COMMENT] mark, the MCU 30 proceeds from S112 to S118.

[0163] In S118, the MCU 30 captures the value of the cell as comment information and copies the comment information into the corresponding count cell 224 in the count table 55. After that, the MCU 30 proceeds from S118 to S116. <zusammenfassung>[View 1]

[0164] The head device 1a is an example of a capture section that captures an image of colonies generated in a test body. Note that the MCU 30 can function as a capture section by reading a colony image file assigned by a user. The MCU 30 functions as an execution section that executes first software (for example, the application program 39), which performs the processing of counting the number of colonies from the colony image. The MCU 30 functions as a reading section that reads a user file (for example, the configuration file 210) containing information in a matrix format and created by second software (for example, the spreadsheet program 4) different from the first software for counting the colonies generated in the test body or managing a colony count result.Furthermore, the MCU 30 functions as a creation section that creates the counting table 55 used for colony counting based on the user file. Since the configuration file 210 created by the spreadsheet program 41, which is different from the application program 39 that controls the colony counter 1, is converted into the counting table 55, the user's workload for creating the counting table 55 is reduced. As a result, the user's workload for colony counting is reduced. [View 2]

[0165] The storage device 35 functions as a storage area that stores a variety of test settings (e.g., General Viable Bacteria [Background: white], General Viable Bacteria / Setting 2, Escherichia coli group / dark culture medium) applied to the test body. As shown in Fig. As shown in Figure 20, the count table 55 includes a first cell indicating a type of test body, a second cell indicating a cultivation condition (e.g., a dilution factor) applied to the test body, and a third cell (e.g., the count cell 224) containing a count result of the colonies counted by applying the cultivation condition suggested by the second cell to the test body suggested by the first cell. The MCU 30, acting as a creation section, assigns the third cell to any one of the plurality of test settings based on information described at a position in the user file assigned to the third cell (e.g., a cell with a test name in the cell group CG3). As a result, the count cell 224 can be linked to the test setting using the configuration file 210. [View 3]

[0166] As in Fig. 19, the user file may include a first cell group (e.g., CG1 or the like) containing type information indicating the type of the test body, a second cell group (e.g., CG2 or the like) indicating a cultivation condition to be applied to the test body, and a third cell group (e.g., CG3 or the like) containing setting information identified by a combination of the type of the test body and the cultivation condition and associated with an imaging condition for acquiring an image to be applied to the test body or an image processing setting to be applied to the image.The MCU 30, which functions as a creation section, can create the counting table 55 by incorporating the type information (e.g., sandwich set) stored in the first cell group as the name of a test specimen into the counting table 55, and incorporating a name (e.g., 1:10, 1:100, or the like) of the cultivation condition stored in the second cell group as the cultivation condition into the counting table 55. In this way, since a cell of the configuration file 210 corresponds to a cell of the counting table 55, the user can create the configuration file 210 with knowledge of the counting table 55. [View 4]

[0167] The image processing setting may include a detection sensitivity (e.g., binarization sensitivity) to detect a colony as a counting target from the image, or an exclusion threshold (e.g., a threshold for removing small particles) of a particle image excluded from the counting target from the image. [View 5]

[0168] The storage device 35 can function as a storage area that stores a plurality of pre-prepared setting information. Each cell of the third cell group can be associated with any of the plurality of setting information stored in the storage area based on an input value (for example, a name assigned to a test setting, the [PROBE DB] tag, a combination of the [IN] tag and the [MEDIUMTYPE] tag, and the like) of the cell. In this way, the user can easily assign a test setting because there is one degree of freedom in a method for determining the test setting. [View 6]

[0169] In the counting table 55, the counting cell 224, into which a counting result is input for each combination of the test body and the cultivation condition, can be linked to setting information assigned to a cell corresponding to the counting cell in the third cell group of the user file. The MCU 30 clicks the icon 225 of the counting cell 224 in the counting table 55 to apply the test setting assigned to the counting cell 224 and cause the colony counter 1 to perform a count. The connection between the counting cell 224 and the test setting can be direct or indirect. In the former case, at the time of creating the counting table 55, a test setting can be identified by a test designation cell of the cell group CG3 in the configuration file 210, and the identified test setting can be linked to the counting cell 224.In the latter case, the count cell 224 may refer to the test label cell of cell group CG3 in the configuration file 210, and when the icon 225 is pressed, the MCU 30 may identify a test label cell associated with the count cell 224 and further identify the test setting associated with the test label cell. [View 7]

[0170] The third cell group in the user file has a test label cell associated with count cell 224 in count table 55. The test label cell may contain a first character string (for example, [ON]). As shown in Fig. 19, a fourth cell group (e.g., CG4) in the user file may include a cell associated with any one of the plurality of test settings. The cell is, for example, a cell (e.g., the [MEDIUMTYPE] tag or a cell in a row where the [FAVORITES] tag is present) that corresponds to the first character string (e.g., [ON]) described in the test label cell. A character string (a name of the test setting (e.g., General Viable Bacteria [Background: white])) may be described in the cell. A test setting (e.g., General Viable Bacteria / Setting 1) associated with the character string described in this cell may be connected to the count cell 224.In this way, a string (for example, [ON]) indicating that a default test setting is assigned can be described in the test label cell. [View 8]

[0171] The plurality of test settings may include a test setting uniquely created or selected by the user in accordance with the cultivation condition. As described above, the user may register some of the plurality of test settings as favorites. The test label cell associated with the count cell 224 in the count table 55 in the third cell group in the user file may contain a second character string (for example, [ON]). In this case, a fifth cell group (for example, CG5) included in the user file is referenced. The fifth cell group also includes a cell associated with any one of the plurality of test settings (for example, a cell describing a character string of Escherichia coli group / dark culture medium).The MCU 30 assigns the counting cell 224 to a test setting (e.g., Escherichia coli group / dark culture medium) associated with the cell containing the second character string. Note that in the case of . Fig. 19, a standard test setting name is described in cell group CG4, and the names of the test settings registered as favorites are described in cell group CG5. In the case of FIG. 19, the test setting names are described only in cell group CG4 or CG5. Therefore, when the [ON] tag is described in cell group CG3, the test setting names described in cell group CG4 or CG5 are identified. If the test setting names are described in both cell groups CG4 and CG5, the test setting names described in cell group CG5 can be adopted preferentially. [View 9]

[0172] As in Fig. 26, the test label cell associated with the count cell 224 in the third cell group may contain a third character string (e.g., [SAMPLE DB]). In this case, the MCU 30 associates the count cell 224 with a test setting associated with the test item (e.g., the sample name) of the test label cell associated with the count cell 224 from the plurality of test settings. In this way, the count cell 224 may be associated with the test setting stored in the sample DB 40 or the like using the configuration file 210. [View 10]

[0173] The test setting can be for each of the species (e.g., general viable bacteria, Escherichia coli group, and Staphylococcus aureus) of bacteria forming the colonies. The cultivation condition applied to the test body can include one bacterial species. [View 11]

[0174] The cultivation condition applied to the test body may include a combination of a bacterial species and a dilution factor. [View 12]

[0175] As in Fig. 19 and the like, the third cell group (e.g., CG3) in the user file may include a plurality of cells having different dilution factors for a test body type. Each of the plurality of cells may include a character string suggesting a test setting associated with a combination of the test body type and the dilution factor. Fig. 19 is assigned that a count is performed with three dilution factors (1:10, 1:100, and 1:1000) for the sandwich set. In this case, there are three test label cells for three combinations each. Fig. 19 is described in each of the three test name cells [ON], but a test setting name such as General Viable Bacteria / Set 2 can also be assigned. Furthermore, the character strings assigned in the three test name cells are not necessarily identical. That is, the three combinations can be assigned to different test settings. [View 13]

[0176] The user file may include a cultivation condition in which a multiple counting mode (for example, the fast mode) in which a first count is performed when a predetermined time shorter than a prescribed cultivation time elapses, and a second count is performed when the prescribed cultivation time elapses, is set as valid. In Fig. 19, the fast mode is set as valid by the [EARLY] tag and the [ON] tag.

[0177] As in Fig. As shown in Figure 20, the creation section (the MCU 30) can create the counting table 55, which includes a first counting cell of column 227 containing a result of the first count and a second counting cell of column 228 containing a result of the second count for the same test specimen. In this way, a plurality of columns are automatically arranged in the counting table 55 according to the mode by creating only one column in the configuration file 210. [View 14]

[0178] The acquisition section may include an imaging section (e.g., the main camera 11) that captures the test specimen and generates a test image of the test specimen. The MCU 30 may include a setting section that sets a first detection parameter for detecting colonies from a first test image of the test specimen cultured for the predetermined time and a second detection parameter for detecting colonies from a second test image of the test specimen cultured for the prescribed culture time. A detection sensitivity of the first detection parameter is higher than a detection sensitivity of the second detection parameter.The MCU 30 can detect the colonies by applying the first detection parameter to the first test image and inputting an intermediate result into the first counting cell of column 227, and detect the colonies by applying the second detection parameter to the second test image and inputting a final result into the second counting cell of column 228. [View 15]

[0179] As in Fig. As shown in Figure 24, the test body can be accommodated in a test container (the Petri dish 15) which is divided into a plurality of accommodation areas by a partition wall. As shown in Fig. As shown in Figure 25, the third cell group in the user file may include a cell for each of the housing areas, where the cell is identified by a combination of the test body type, the cultivation condition, and the housing area. The cell for each of the housing areas may include a character string (e.g., "Upper Left Detection") suggesting a test setting to be applied to each of the housing areas. [View 16]

[0180] As mentioned with reference to Fig. 25, in the third cell group of the user file, a test setting suggested by a character string (e.g., "Upper Left Detection") stored in a cell associated with a first accommodation area (e.g., the upper left effective area 231) of the plurality of accommodation areas includes excluding a remaining area (e.g., the effective areas 232 to 234) that is not the first accommodation area of the plurality of accommodation areas from the counting target.In the third cell group of the user file, a test setting suggested by a character string (e.g., "Lower Left Detection") stored in a cell associated with a second accommodation area (e.g., the lower left effective area 234) of the plurality of accommodation areas includes excluding a remaining area (e.g., the effective areas 231 to 233) that is not the second accommodation area of the plurality of accommodation areas from the counting target. [View 17]

[0181] As mentioned with reference to Fig. 22, the MCU 30 may function as a copy section that copies a count result into a test label cell corresponding to the count cell 224 in the configuration file 210 when the count result is input into the count cell 224 comprising the count table 55. Furthermore, the MCU 30 may copy the count result into the store file 200. [View 18]

[0182] As mentioned with reference to Fig. 23, the creation section (the MCU 30) may create the count table 55 when an empty cell is found in the first cell group (for example, CG1), ignoring a row including the empty cell. [View 19]

[0183] As mentioned with reference to Fig. 27, there is a case where the creation section (the MCU 30) finds a tag (for example, the [REPEAT:n] tag) indicating that counting is performed n times for the same test body and a statistical value (for example, an average or a standard deviation) of n counting results is obtained in the configuration file 210. In this case, the MCU 30 may arrange n cells for storing the n counting results and one cell for storing the statistical value in the counting table 55. [View 20]

[0184] As mentioned with reference to Fig. 28, the creation section (the MCU 30) may link a test setting to the counting cell 224 in which a counting result is stored in the counting table 55 based on a character string described in a cell located at a predetermined coordinate (for example, B1, C1, B3, C3, B5, C5, or A6 to A7) in the configuration file 210. [View 21]

[0185] As mentioned with reference to Fig. As described in Figure 29, at least one parameter (for example, sensitivity: 5.5, small particle removal: 0.3, image brightness: 150, or the like) among a plurality of parameters constituting a test setting can be described in a cell comprising the third cell group. In this case, the creation section (the MCU 30) can adapt a part of the test setting assigned to the cell to the parameter assigned in the cell, and then link the test setting to the count cell 224 corresponding to the cell in the count table 55. [View 22]

[0186] The user file can be a CSV format file created with a spreadsheet program (for example, spreadsheet program 41), which is the second software, or a file in a special spreadsheet format (for example, the xslx format) of the spreadsheet software. In particular, the xslx format is widely used on the market, and many users are familiar with it. Therefore, users can easily create the configuration file 210, which serves as the basis for the counting table 55, with familiar spreadsheet software. [View 23]

[0187] As in Fig. 19, the configuration file 210 is an example of a configuration file that contains information in a plurality of cells with N rows × M columns. The configuration file 210 may include a first cell that stores a type (e.g., the sample name) of a test body, a second cell that stores a cultivation condition (e.g., a dilution factor) of the test body, a third cell (e.g., a cell in a row containing the [NAME] tag) that stores a bacterial species to be detected, and a fourth cell that is identified by a combination of the type of test body, the cultivation condition of the test body, and the bacterial species to be detected, and suggests a test setting.The fourth cell may, for example, be a test designation cell assigned to cell group CG3, a cell in a row that includes the [MEDIUMTYPE] label, or a cell in a row that includes the [FAVORITES] label. The MCU 30 functions as a reading section that reads the configuration file 210. The storage device 35 can store a plurality of test settings corresponding at least to the type of test body and the type of bacteria to be detected, in order to identify an individual test setting corresponding at least to the type of test body and the type of bacteria to be detected.The MCU 30 functions as a count table generation section, which generates the count table 55 including a plurality of candidate count cells (for example, the count cell 224) in which a count result is to be stored, the count result being counted by a test based on the type of test body, the cultivation condition of the test body, the bacterial species to be detected, and the test setting proposed by the fourth cell, which is defined by the combination of the type of test body, the cultivation condition of the test body, and the bacterial species to be detected from the plurality of test settings included in the configuration file 210 read by the reading section.Here, each of the plurality of candidate count cells is identified by the combination of the type of test body, the cultivation condition of the test body, and the bacterial species to be detected. The display control section 36 functions as a display control section that displays the count table 55 generated by the count table generation section (MCU 30) on a display section (e.g., the display device 37). The pointing device 33 functions as a cell identification section that identifies a count cell from among the plurality of candidate count cells included in the count table 55 displayed by the display control section 36, into which a count result is input. The MCU 30 functions as a test execution section that acquires a test image, which is an image of the test body based on a test setting, and counts the colonies included in the test image.In addition, the MCU 30 functions as a count table editing section that assigns a count result of the colonies counted by the test execution section to the one cell identified by the cell identification section. [View 24]

[0188] The MCU 30 functions as a reading section that reads a configuration file that includes a test body type, a culture condition of the test body, and a bacterial species to be detected as elements of either a row or a column, and has a first test setting corresponding to a field defined by the elements. The storage device 35 stores a second test setting corresponding to at least the test body type and the bacterial species to be detected to identify an individual test setting corresponding to each of the types of a plurality of test bodies and each of the plurality of bacterial species to be detected.The MCU 30 may function as a count table generating section that generates the count table 55 including a plurality of candidate count cells in which a count result is to be stored, the count result being determined by a test based on the type of test body, the cultivation condition of the test body, the bacterial species to be detected, and the first test setting (for example, information for designating a test setting stored in the cell group CG3) corresponding to the field defined by a combination of the type of test body, the cultivation condition of the test body, and the bacterial species to be detected included in the configuration file read by the reading section, and the second test setting (for example, an actual test setting) corresponding to the first test setting and stored in the storage area.

[0189] The invention is not limited to the above embodiment, and various modifications and changes may be made within a basic spirit of the invention. QUOTES CONTAINED IN THE DESCRIPTION

[0000] This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions. Cited patent literature

[0000] JP 2015-171334 A

[0003] < / zusammenfassung>

Claims

[1] Colony counting device comprising: a detection section configured to capture an image of the colonies generated in a test body; and an execution section configured to execute a first software, the execution section being configured to perform counting processing of a number of the colonies from the image of the colonies, wherein the execution section comprises: a reading section configured to read a user file containing information in a matrix format and generated by a second software different from the first software to count the colonies generated in the test body or to manage a colony count result; and a creation section configured to create a counting table used to count colonies based on the user file. [2] A colony counting device according to claim 1, further comprising a storage unit configured to store a plurality of test settings applied to the test body, wherein the counting table comprises a first cell indicating a type of the test body, a second cell indicating a cultivation condition applied to the test body, and a third cell containing a counting result of the colonies counted by applying the cultivation condition suggested by the second cell to the test body suggested by the first cell, and the creation section links the third cell to any one of the plurality of test settings based on information described at a location in the user file corresponding to the third cell. [3] Colony counting device according to claim 1, wherein the user file includes: a first cell group having type information indicating a type of the test body; a second cell group indicating a cultivation condition for the test body; and a third cell group containing a test setting identified by a combination of the type of test body and the cultivation condition, the test setting being associated with an imaging condition for acquiring the image applied to the test body or an image processing setting applied to the image, and the creation section creates the counting table by adopting the type information stored in the first cell group as a test body name in the counting table and adopting a name of the cultivation condition stored in the second cell group as a cultivation condition in the counting table. [4] A colony counting device according to claim 3, wherein the setting of the image processing comprises a detection threshold for detecting a colony as a counting target from the image or an exclusion threshold of a particle image excluded from the counting target from the image. [5] A colony counting device according to claim 3, further comprising a storage area configured to store a plurality of pre-prepared test settings, wherein each cell of the third cell group is associated with any one of the plurality of test settings stored in the storage area based on an input value for each cell. [6] A colony counting device according to claim 5, wherein, in the counting table, a counting cell into which a counting result is input for each combination of the test body and the cultivation condition is assigned to the test setting assigned to a cell corresponding to the counting cell in the third cell group of the user file. [7] A colony counter according to claim 6, wherein, when the count cell corresponding to the count cell in the count table in the third cell group of the user file contains a first character string, the count cell is associated with a test setting associated with a cell corresponding to the first character string in a fourth cell group containing a cell associated with any one of the plurality of test settings, the fourth cell group being included in the user file. [8] Colony counting device according to claim 6, wherein the plurality of test settings includes a test setting created or selected by a user in accordance with the cultivation condition, and if the count cell corresponding to the count cell in the count table contains a second character string in the third cell group of the user file, the count cell is associated with a test setting associated with a cell corresponding to the second character string in a fifth cell group containing a cell associated with any one of the plurality of test settings, the fifth cell group being included in the user file. [9] A colony counting device according to claim 6, wherein, when the cell corresponding to the counting cell in the third cell group contains a third character string, the counting cell is associated with a test setting associated with the test body of the cell corresponding to the counting cell among the plurality of test settings. [10] The colony counting device according to claim 1, wherein, when the user file includes a cultivation condition in which a multiple counting mode in which a first counting cell is executed when a predetermined time shorter than a prescribed test setting elapses and a second counting cell is executed when the prescribed test setting elapses, the creating section creates a counting table including a first counting cell containing a result of the first count and a second counting cell containing a result of the second count for the same test body. [11] A colony counting device according to claim 10, wherein: the detection section comprises an imaging section configured to capture the test body and generate a test image of the test body, the execution section comprises a setting section configured to set a first detection parameter for detecting the colonies from a first test image of the test body cultivated for the predetermined time and a second detection parameter for detecting the colonies from a second test image of the test body cultivated for the prescribed cultivation time, a detection sensitivity of the first detection parameter is higher than a detection sensitivity of the second detection parameter, and the execution section further counts the colonies by applying the first detection parameter to the first test image and inputs an intermediate result into the first counting cell and counts the colonies by applying the second detection parameter to the second test image and inputs a final result into the second counting cell. [12] A colony counting device according to claim 3, wherein: the test body is housed in a test container which is divided into a plurality of accommodation areas by a partition wall, and the third cell group of the user file comprises a cell for each of the accommodation areas, the cell being identified by a combination of the type of test body, the cultivation condition and the accommodation area, and the cell for each of the accommodation areas comprises a character string suggesting a test setting applied for each of the accommodation areas. [13] A colony counting device according to claim 12, wherein: in the third cell group of the user file, a test setting suggested by a character string stored in a cell associated with a first accommodation area of the plurality of accommodation areas comprises the exclusion of a remaining area of the plurality of accommodation areas from a counting target that is not the first accommodation area, and in the third cell group of the user file, a test setting suggested by a character string stored in a cell associated with a second accommodation area of the plurality of accommodation areas comprises excluding from the counting target a remaining area of the plurality of accommodation areas that is not the second accommodation area. [14] The colony counting apparatus according to claim 3 further comprises a copying section configured to copy a counting result into a counting cell in the user file corresponding to a counting cell when the counting result is inputted into the counting cell included in the counting table. [15] A colony counting apparatus according to claim 1, wherein the preparation section arranges n cells for storing n counting results and a cell for storing a statistical value in the counting table when a mark indicating that counting is carried out n times for the same test body is found in the user file and the statistical value of the n counting results is obtained. [16] The colony counting apparatus according to claim 1, wherein the creating section links a test setting to a counting cell in which a counting result is stored in the counting table based on a character string described in a cell located at a predetermined coordinate in the user file. [17] A colony counting apparatus according to claim 3, wherein, when at least one parameter of a plurality of parameters constituting a test setting is described in a cell included in the third cell group, the creating section adapts a part of the test setting associated with the cell to the at least one parameter and then links the test setting to a counting cell corresponding to the cell in the counting table. [18] The colony counting device according to claim 1, wherein the user file is a CSV format file created with spreadsheet software that is the second software, or a file in a unique spreadsheet format of the spreadsheet software. [19] Colony counting device comprising: a reading section configured to read a configuration file containing information in a plurality of cells of N rows × M columns, the configuration file comprising a first cell storing a type of test body, a second cell storing a cultivation condition of the test body, a third cell storing a bacterial species to be detected, and a fourth cell identified by a combination of the type of test body, the cultivation condition of the test body, and the bacterial species to be detected and suggesting a test setting; a memory area configured to store a plurality of test settings corresponding at least to the type of test body and the type of bacteria to be detected, to identify an individual test setting corresponding at least to the type of test body and the type of bacteria to be detected; a count table generation section configured to generate a count table including a plurality of candidate count cells in which a count result is to be stored, the count result being counted by a test based on the type of test body, the cultivation condition of the test body, the bacterial species to be detected, and the test setting proposed by the fourth cell, which is defined by the combination of the type of test body, the cultivation condition of the test body, and the bacterial species to be detected, among the plurality of test settings included in the configuration file read by the reading section, each of the plurality of candidate count cells being identified by the combination of the type of test body, the cultivation condition of the test body, and the bacterial species to be detected; a display control section configured to display the count table generated by the count table generating section on a display section; a cell identifying section configured to identify, from among the plurality of candidate counting cells included in the counting table displayed by the display control section, a counting cell into which the counting result is input; a test execution section configured to acquire a test image that is an image of the test body based on the test setting and the counting colonies included in the test image; and a count table editing section configured to assign the count result of the colonies counted by the test execution section to the one cell identified by the cell identification section. [20] Colony counting device comprising: a reading section configured to read a configuration file having a type of test body, a cultivation condition of the test body, and a bacterial species to be detected as elements of either a row or a column, and having a first test setting corresponding to a field defined by the elements; a memory area configured to store a second test setting corresponding to the type of test body and / or the bacterial species to be detected, to identify an individual test setting corresponding to each of the types of a plurality of test bodies or each of a plurality of bacterial species to be detected; a count table generating section configured to generate a count table including a plurality of candidate count cells in which a count result is to be stored, the count result being counted by a test based on the type of test body, the cultivation condition of the test body, the bacterial species to be detected, and the first test setting corresponding to the arrangement defined by a combination of the type of test body, and the first test setting corresponding to the arrangement defined by a combination of the type of test body, the cultivation condition of the test body, and the bacterial species to be detected included in the configuration file read by the reading section, and the second test setting corresponding to the first test setting and stored in the storage area, wherein each of the plurality of candidate counting cells is identified by the combination of the type of test body, the cultivation condition of the test body, and the bacterial species to be detected; a display control section configured to display the count table generated by the count table generating section on a display section; a cell identifying section configured to identify, from among the plurality of candidate count cells included in the count table displayed by the display control section, a cell into which the count result is input; a test execution section configured to acquire a test image that is an image of the test body based on the second test setting and includes counting colonies included in the test image; and a count table editing section configured to assign the count result of the colonies counted by the test execution section to the cell identified by the cell identification section.

Images