| [21:05:53] | * JustTB has quit (Quit: Leaving.) |
| [21:21:22] | * JustTB has joined #farmos |
| [22:48:35] | * JustTB has quit (Quit: Leaving.) |
| [04:28:48] | * JustTB has joined #farmos |
| [05:08:39] | * JustTB has quit (Quit: Leaving.) |
| [05:27:05] | * JustTB has joined #farmos |
| [08:28:39] | * trentf has quit (Remote host closed the connection) |
| [08:46:50] | * trentf has joined #farmos |
| [10:21:28] | * cpm has joined #farmos |
| [11:33:05] | * alexas[m] has joined #farmos |
| [11:34:10] | <alexas[m]> | Howdy - anyone here? |
| [11:34:21] | * jgaehring[m] has joined #farmos |
| [11:34:22] | <alexas[m]> | Hi Jamie! |
| [11:34:27] | <jgaehring[m]> | oh hey there! |
| [11:34:31] | <jgaehring[m]> | just exploring riot |
| [11:34:47] | <jgaehring[m]> | looks like there's another room for the farmos/offline |
| [11:35:05] | <alexas[m]> | ooh, ok |
| [11:37:25] | <alexas[m]> | I moved over to farmOS native |
| [12:17:01] | <chrowe[m]> | Is there a way to export sensor data? |
| [12:20:20] | <mstenta[m]> | chrowe: there is currently a CSV export button that you can use to manually export |
| [12:20:31] | <mstenta[m]> | Other option is to do a raw SQL query (but only if you have access to the db) |
| [12:20:42] | <chrowe[m]> | I don't see it :( |
| [12:21:16] | <mstenta[m]> | Oh?... |
| [12:22:14] | <mstenta[m]> | (investigating...) |
| [12:23:00] | <mstenta[m]> | DOH! |
| [12:23:01] | <mstenta[m]> | I was wrong... we DON'T have that... |
| [12:23:06] | <mstenta[m]> | It won't be hard to add, though |
| [12:23:32] | <mstenta[m]> | chrowe: do you need some data specifically? I can get it to you directly in the meantime... |
| [12:23:43] | <mstenta[m]> | Adding a feature request right now for the CSV export so I don't forget |
| [12:28:18] | * farmBOT has joined #farmos |
| [12:29:11] | <mstenta[m]> | https://www.drupal.org/project/farm/issues/2950502 |
| [12:38:51] | <chrowe[m]> | No need for data right now mstenta I was just thinking about Pivot tables and wanted to test some real sesnor data in a spreadsheet. For Drupal there |
| [12:38:52] | <chrowe[m]> | is https://www.drupal.org/project/views_pivot |
| [12:39:59] | <mstenta[m]> | Oh interesting! That modules seems vaguely familiar - I think RJ and I may have stumbled across that when we were discussing all this stuff |
| [12:40:50] | <mstenta[m]> | I think I'm leaning towards the "pre-defined columns" idea we talked about on the phone |
| [12:40:58] | <mstenta[m]> | That would actually solve a couple of things |
| [12:41:02] | <mstenta[m]> | You could add a better name to each column |
| [12:41:08] | <mstenta[m]> | And also define what the units are |
| [12:41:17] | <mstenta[m]> | And from there you could maybe do fancy stuff like C to F conversion (maybe offer the ability for conversion plugins to be provided, so modules could add their own) |
| [12:42:33] | <mstenta[m]> | Actually come to think of it, I described this idea here a while ago: https://www.drupal.org/project/farm/issues/2912481 |
| [12:42:41] | <mstenta[m]> | (in the first comment - not the issue description) |
| [12:43:29] | <mstenta[m]> | That actually outlines some of the other considerations... |
| [12:43:33] | <mstenta[m]> | Stuff to think about |
| [12:43:45] | <mstenta[m]> | For now, I'm going to focus on the graphing, and probably add API endpoint(s) for getting data for the graphs... |
| [12:44:10] | <mstenta[m]> | But I'm eager to think more about the db structure too |
| [12:44:52] | <chrowe[m]> | Ya, not sure pivot tables do what we want anyway. +1 for graphs |
| [12:47:06] | <cpm> | ACTION ponders some kinda report generator |
| [12:48:02] | <mstenta[m]> | Hmm just had a potential idea to solve one of the considerations there: https://www.drupal.org/project/farm/issues/2912481#comment-12512628 |
| [12:48:43] | <mstenta[m]> | cpm: Mm yea that would be great! Especially if it could query sensor data from different sensors |
| [12:48:50] | <mstenta[m]> | Ie: by location or something? |
| [12:48:52] | <mstenta[m]> | Need to think through some use-cases |
| [12:50:26] | <cpm> | yeah, kinda all the same. Wanted to look at categorizing/compartmentalizing gis/sensor data |
| [12:51:13] | <dornawcox[m]> | From Josh at Wolfes Neck regarding Grazing module- As far as the quick birth form goes, it seems like the system is having trouble recognizing the mother and father that I am putting in the form. I can't create any new animals through that form right now because of that |
| [12:51:58] | <dornawcox[m]> | Rather the quick form. Wolfes neck could also test the egg module... |
| [12:52:53] | <mstenta[m]> | @dornawcox:matrix.org: Thanks! When did Josh give you that feedback? I actually just fixed that issue this morning. :-) |
| [12:53:33] | <mstenta[m]> | Enabling farm_eggs now... |
| [12:53:39] | <cpm> | heh |
| [12:53:49] | <mstenta[m]> | Done: https://wolfesneck.farmos.net/farm/quick/eggs |
| [12:56:45] | <cpm> | neat |
| [13:02:10] | * skidsteerpilot has joined #farmos |
| [13:02:21] | <jlharlan1s[m]> | The egg quick form works great! |
| [13:03:33] | <mstenta[m]> | jlharlan1s: great! |
| [13:03:58] | <mstenta[m]> | jlharlan1s: are you Josh from Wolfe's Neck? |
| [13:04:44] | <jlharlan1s[m]> | The birth form still isn't recognizing my cow names. It wants the animal asset id. Yes I am from Wolfe’s Neck |
| [13:06:01] | <mstenta[m]> | jlharlan1s: Cool nice to meet you! :-) |
| [13:06:03] | <mstenta[m]> | OK hmm |
| [13:06:16] | <mstenta[m]> | Does a dropdown appear when you start to type an animal name? |
| [13:06:33] | <mstenta[m]> | If so, click on the one you want in the dropdown list |
| [13:06:43] | <mstenta[m]> | This will populate the field, and will also include an "[id: X]" tag on it |
| [13:06:57] | <mstenta[m]> | Which is necessary for the form to know what animal you want to reference (in case two animals have the same name) |
| [13:08:02] | <mstenta[m]> | jlharlan1s: for example "Edith [id: 44]" |
| [13:08:26] | <mstenta[m]> | The "[id: 44]" part is necessary |
| [13:08:51] | <mstenta[m]> | I will look to see if there's a more intuitive way to do that... so that it isn't required, because that is sort of confusing |
| [13:12:04] | <jlharlan1s[m]> | That makes sense. It is working just like you said. |
| [13:12:47] | <cpm> | for the fun of things, viz sensor data access: |
| [13:12:52] | <jlharlan1s[m]> | I am still having difficulty with putting our bulls into the system. They aren't real animals on the farm but I want to be able to reference them as a parent for record keeping |
| [13:12:55] | <cpm> | is there a GODAN pub on data format? |
| [13:14:09] | <mstenta[m]> | jlharlan1s: Great! Glad that works |
| [13:14:31] | <mstenta[m]> | jlharlan1s: Regarding bulls... |
| [13:14:50] | <mstenta[m]> | You could just add them as animals, but "archive" them immediately, since you don't need them for anything other than a reference. |
| [13:15:26] | <mstenta[m]> | That would allow you to still keep track of separate bulls for lineage purposes, without seeing them in the list of active animals. |
| [13:15:31] | <cpm> | jlharlan1s[m], side note, are your animals rfid'd? |
| [13:15:51] | <mstenta[m]> | And if you ever needed to, you could open up their animal record and record logs on it - like Observations or something if there were some breeding quality observations you wanted to keep perhaps. |
| [13:16:24] | <mstenta[m]> | cpm: I'm not sure. |
| [13:16:53] | <cpm> | it's not at all important, just curios (viz another/related project) |
| [13:29:14] | <jlharlan1s[m]> | mstenta: I see. Looks like that has fixed that issue! |
| [13:29:33] | <dornawcox[m]> | I believe the wolfes neck cows all have RFID tags for the dairymaster milking system, but the data logger has not been set up yet. Josh and I were just saying that that should be our next IOT project to push to FarmOS. |
| [13:31:14] | <mstenta[m]> | Cool! @dornawcox:matrix.org and jlharlan1s let me know if you start to explore that! Paicines Ranch is interested in the same thing. |
| [13:31:36] | <mstenta[m]> | Specifically for taking automated weight measurements on the scale |
| [13:32:01] | <mstenta[m]> | That would be a great project to bring donblair and chrowe in on! |
| [13:32:30] | <mstenta[m]> | I mentioned it to donblair a while back and he had some ideas already - we have them in an email thread somewhere |
| [13:34:21] | <jlharlan1s[m]> | cpm: our animals have the tags but our Rfid reader isn't operational currently for various reasons. We do have some manually kept milk production records that we'd like to put into FarmOS |
| [13:35:33] | <cpm> | jlharlan1s[m], thanks. |
| [13:36:16] | <mstenta[m]> | jlharlan1s: If you have old data like that, the harvest importer might be the best way to do it |
| [13:36:37] | <mstenta[m]> | I could take a look at your data sometime and give you a better answer, if that would be helpful |
| [13:37:02] | <mstenta[m]> | Should also think about what's the easiest method for entering new data moving forward - whether that's just using the raw harvest logs, or creating another Quick Form |
| [13:37:11] | <mstenta[m]> | Or automated1 |
| [13:42:01] | <jlharlan1s[m]> | With the rfid, the computer program running the reader should be able to put it directly into an excel sheet of some sort |
| [13:42:27] | <cpm> | does your milking equp log? |
| [13:45:35] | <mstenta[m]> | jlharlan1s: Ok, so then we may be able to just import that spreadsheet |
| [13:45:37] | <jlharlan1s[m]> | Not currently. I have been told that the system needs to have a computer running with the reader constantly to log the milk data |
| [13:47:36] | <dornawcox[m]> | jlharlan1s: I believe the rfid reader equipment is in place, but not set up. Is that correct? |
| [13:48:24] | <jlharlan1s[m]> | @dornawcox:matrix.org: I think that is correct |
| [13:52:22] | <mstenta[m]> | jlharlan1s: regarding " the system needs to have a computer running with the reader constantly" - perhaps that could be a cheap Raspberry Pi computer that connects directly to farmOS - so the data streams right to its final destination |
| [13:54:07] | <mstenta[m]> | (unless it requires a proprietary windows-based software... then less easy) |
| [13:54:54] | <jlharlan1s[m]> | I think that would do it. In the current system we've had trouble with water. The connection for the computer is in a wet environment of the milk house. I'm not sure what the system requires. I've never actually seen it run. |
| [13:55:03] | <cpm> | I would imagine so. |
| [13:55:10] | <dornawcox[m]> | I am almost on site, and will check it out this afternoon (hopefully with Josh) |
| [13:56:22] | <jlharlan1s[m]> | ACTION posted a file: Calculating-Paddock-Sizes-Dry-Matter-Intake-and-Acreage-Needed.pdf (560KB) <https://matrix.org/_matrix/media/v1/download/matrix.org/JyPeKormjpjPMNhA... |
| [13:57:07] | <jlharlan1s[m]> | ACTION sent a long message: jlharlan1s[m]_2018-03-06_18:57:07.txt <https://matrix.org/_matrix/media/v1/download/matrix.org/cSXrASmMdQIsBsfd... |
| [13:57:55] | <mstenta[m]> | jlharlan1s: Ok well if a Raspberry Pi will work, it's easy to put that in a water-resistant electrical junction box enclosure |
| [13:59:09] | <mstenta[m]> | jlharlan1s: That's really great feedback. Let's create feature requests for those so we can bring them up in the next planning sessions... |
| [13:59:14] | <jlharlan1s[m]> | As far as the later part of that message goes, I uploaded a PDF from our dairy consultant about calculating paddock size. The most pertinent page of the PDF will be the last one with information about the actual calculations that we run at the beginning of the grazing season |
| [13:59:17] | <mstenta[m]> | Here is the Github repo for the grazing module: |
| [13:59:20] | <mstenta[m]> | https://github.com/mstenta/farm_grazing |
| [13:59:46] | <cpm> | well, , whatever the interface is, I expect a pi or a microcontroller(arduino) could be used to extend it to a place where you could set a computer. |
| [13:59:49] | <jlharlan1s[m]> | mstenta: I think its definitely worth a shot |
| [13:59:51] | <mstenta[m]> | And here's the form for adding a new issue: https://github.com/mstenta/farm_grazing/issues/new |
| [13:59:59] | <mstenta[m]> | If you want to create a github account and add those, please feel free! |
| [14:00:01] | <mstenta[m]> | Otherwise I can do that too |
| [14:00:11] | <cpm> | IE, if it needed 'windows' or something. |
| [14:00:25] | <mstenta[m]> | I like your idea for a page that lets you tweak the assumptions for a plan |
| [14:00:29] | <cpm> | seems unlikely. Prolly serial or usb |
| [14:00:33] | <mstenta[m]> | And maybe we could have some pre-configured for dairy grazing vs beef grazing etc |
| [14:00:52] | <mstenta[m]> | cpm: yea true! |
| [14:11:01] | <mstenta[m]> | jlharlan1s: I'm copying your ideas into new feature requests... |
| [14:11:03] | <mstenta[m]> | https://github.com/mstenta/farm_grazing/issues/35 |
| [14:14:35] | <mstenta[m]> | jlharlan1s: Regarding "In the herds page we need flexibility for the dry matter intake of the animals. Maybe there is another page where we can set assumptions for categories such as 3.5%Bodyweight for Lactating cows, 3% of bodyweight for Dry Cows."... |
| [14:14:58] | <mstenta[m]> | Each animal can be assigned a "type" in the Herds page which corresponds to a dry matter intake factor |
| [14:15:22] | <mstenta[m]> | You can actually add new types to that list |
| [14:15:31] | <mstenta[m]> | Do you think that covers what you described? |
| [14:24:15] | * cpm has quit (Quit: Leaving) |
| [16:35:13] | * skidsteerpilot_ has joined #farmos |
| [16:48:00] | * skidsteerpilot_ has quit (Quit: Page closed) |
| [16:52:34] | * skidsteerpilot has quit (Quit: Page closed) |