u/Extension-Skill652

When I'm thinking of a poster title, I usually want something that is attention grabbing, but also fun. My posters that have had a good amount of people actually come up wanting to talk about the material in depth have always had a tagline at the front of the title (formatted as "TAGLINE: rest of title") and I personally always want that tagline to be a bit of a joke or more casual followed by the more professional portion of the title. My most recent one was a bit strange for the conference it was at (thematically fitting, but computational heavy at a more social science/human dimensions heavy event) but got a lot of interest seemingly because of the title.

I've seen some people do these as well and listed a few below that I've collected as examples. Note that my field is wildlife biology where posters are allowed to be more relaxed especially at smaller events which are surprisingly abundant, but this might not work in your field (aka I will not listen when you say don't do it because Chemistry hates fun of whatever). I'd really like to see examples other people have done themselves or ones you've seen that are a similar style/had similar success.

Examples:

"The girls are fighting: ..." - for competition or displays between females of a species

"To X or not to X: ..." - for comparison between two methods, a play on to be or not to be

"The secret life of X: ..." - for elusive animals

"Hide and sneak: ..." - for elusive animals

"The real X of Y: where are they now?" - for past vs present status, real housewives reference

I have a bit of a specific situation with how my workplace structures SQLite databases that I'm hoping to find a better solution for, mainly related to efficient querying across many database files.

Where I work, we handle a lot of trail camera data (images) that have associated data for what's in the image stored in SQLite databases—all of this is manually filled out as someone goes through image by image. Right now, we're nearing 100 total database files, each storing records for between 300k and 1 million images. We use the program Timelapse from UC Calgary to tag all the images and continually go back in to update things or add new data, so our individual database files have to basically stay as is for this to remain functional.

In the past, we've had people export CSV files from the databases then someone merged them all together with a bunch of really annoying, fragile code. This is, of course, annoying but also doesn't reflect any new changes that happen after that export. I've come in with more expertise in general on programming than they usually get and showed that you can pull things directly from each database with R (we're biologists, that's just the language we're used to). Because of this, we want to come up with a solution that lets us do this across all the databases as needed and stop doing that CSVs.

Right now, running a simple query that results in ~3k rows across most (not all, ~70%) of the individual databases takes about 3 minutes which is fine if you just need a big export, but we'd like to have some interactive visualization tools where a 3 minute wait for something you might decide to change to look at something else right after wouldn't be good for.

Originally I hoped for a way to establish a single connection in a "master" database that would remove some of this latency, but ATTACH which would be the solution isn't going to work for us in about 1-2 years when we exceed the maximum on the number of attachable databases at once. The other potential solution is to have a master database that contains copies of everything in the other database files that updates each night, but we already have issues keeping enough storage available with how much space images take up (and this kinda feels like the lazy solution). For any solution, something we can feasibly manage ourselves after some the initial setup would be preferential because IT can be quite slow to act and we are the ones who will be accessing and editing this data 99% of the time.

Talking to a family member (former IT worker) led me to possibly Microsoft SQL server or some sort of local Oracle database, but unsure if any of this would fit our needs and the suggestions were based on their experience from like 15+ years ago. Whatever we use needs to be able to connect with R since that's what existing pipelines use and many of the ecology-related tools we use aren't in any other language. Really in the end we just want some way to make things run faster and ideally combine things into a single connection point to simplify how we get to the data. Even if it's too complex for us, we still need to give IT a plan with enough details to get them going... or we'll be forever in CSV land.

Really just looking for any guidance since googling didn't get me very far, most people seem to have big issues with write speeds but it actually seems quicker to overwrite a whole column in each of our databases via R than it would be to do a simple query from them all?

One final note: these are currently on a network drive which is probably adding to the latency, but solutions like a local NAS in our office are dubious on if they'd work as a solution or even be in the budget with storage media prices right now.

I have a modeling script that needs to be run in R that can take sometimes a few days to complete when I'm including multiple versions of the models but can just be run in the background. I also have other projects that need to be worked on where I'm editing and running the script as I go, but I'd like to avoid waiting for the modeling script to finish. If I use seperate sessions is this likely to cause issues? As far as I'm aware the packages I'm using are not using multi threading but I am working with large dataset (in the modeling script, usually not that large in the other projects) that would assumedly be using up a lot of ram just to load.

My family has 2 dogs that eat a special wet food due to their age and issues with their teeth (one is now down to none, the other has a hard time chewing) and a younger dog that eats regular kibble typically. We have an issue where the younger dog eats the older dogs' food any chance possible leaving them hungry, and now we have to seperate them by locking the older ones or the younger one in a room while food is out. The older dogs are both grazers that really only eat a bit here and there throughout the day, so this ends up being a majority of the time.

I was looking at food bowls that have a cover unless a dog with the right collar/RFID tag is close, but they all seem weirdly expensive and have a bunch of feature I don't care about like cameras to watch them or automated food dispensing throughout the day (we have to mix their food ourselves a few times a day anyways so the dispenser is useless). Anyone know of a more basic option that would be cheaper? I only really care about blocking the younger dog with the cover from stealing from the elderly.