Attempt to tag games as "AM" or "PM"

Jumping off point for assigning "AM" or "PM" to games in case no one else tackles over the coming week.

This is a good start, but I have two suggestions/questions:

Can we leave the time field unmodified? Instead, it might be better to add a new field called meridiem.
The new field meridiem can have three values: AM, PM or None. Some of your cases call for setting None, which more accurately reflects the "unknown" state of things. (I really want to try to avoid labeling a game time AM/PM unless we're really pretty sure that it is right.)

A simple implementation might actually take two passes through the game data, e.g., on the first pass, label all games we know to be PM, which I think includes any game starting between 12 and 8. (I can't imagine a football game starting between 12AM-8AM EST.) The second pass could go through and look at games that don't have meridiem set yet. The rules might be something like:

If the time is < 12 and there are PM games proceding that game on the same day (with respect to its gsis_id), then it should be classified as AM.
If the time is > 12 and there are PM games preceding that game on the same day (with respect to its gsis_id), then it should be classified as PM.

This could potentially leave games with a None meridiem value. e.g., If a 9:30 game is played on a day where no other games are played.

Thanks.  Here's an update based on your feedback.  It does deviate slightly from your suggestion.  Whereas you state "I can't imagine a football game starting between 12AM-8AM EST." (which I agree with), this does leave almost all Monday night and Thursday night games as None.  I have widened the "I can't imagine" window from 12AM-9AM EST so all 8:25 and 8:30 games are bucketed as PM games.  My thought process was "No way they would force the west coast to wake up at 5:30AM to watch a football game", though they have done 6:30AM so does seem a rather arbitrary argument.
Maybe instead of making a bigger window I should have just handled Monday & Thursday games explicitly.

@ochawkeye Hmm, yeah, that window looks pretty tight to me. I think we should:

Shrink that window (say, even, 12-5).
Assume that all games played during the week are always PM.
Assume that all playoff games are always PM (I think these are usually evening games on Saturday/Sunday).

That's easy enough to do, though I'm hesitant.  An 11:30 AM EST Thanksgiving game seems plausible.

Answered my own question...Just need to let the other rules apply first and only worry about weekday and playoff assumptions if it has still fallen all the way through.

Right... Forgot about thanksgiving. Haha. But yeah, thankfully, Thanksgiving has multiple games. :-)

With this method, I'm not even sure that a hour constraint need to be applied.  Commenting out lines 84 & 85 should still catch all games (I think)

@ochawkeye Really? Aren't those times needed for seeding? e.g., For a 9:30AM game, it needs to be able to find those later PM games, but those later games are only PM if we start with the assumption that 12-5 is always PM, right? Does commenting them out cause no change?

No, you're right.  It works this week because there is an AM game (it sees there is a later game that "looks like" and earlier start time so assigns that one AM and all of the afternoon games see the earlier game that "looks like" a later start time so assigns those PM), but a week that doesn't have an AM game would be None across the board.
My bad.  Definitely need to leave that first pass hour scan window in there.

@ochawkeye OK, I buy it. The code is gorgeous, nice work!

I really appreciate that.
git101 question - was there I way I could have/should have made the pull request that would have bundled those 5 commits into a single line item so as to obfuscate my ineptitude in trying to piece this together step-by-step?  Or is this a case where once an immature PR gets posted (like 14ed8f9) each subsequent partial commit is going to get documented?

@ochawkeye There are two different schools of thought on that. Me personally, I like having PRs squashed into a single commit. You could have done that by rebasing your branch on to master (git rebase master), and then force pushing it. It would automatically update the PR.
However, another school of thought says that your progress through the change should be recorded.
All in all, I'm not going to make a stink about it for this repo. If we end up some day with lots of contributors, then ya, it might be worth creating a policy or something and following it, but I'm happy to wing it for now. :-)

FYI - out of 2312 games in the schedule currently, this leaves 78 preseason and 7 regular season games with unassigned meridiems.
Regular season games:
2009121900: Saturday 8:20
2010122500: Saturday 7:30
2011121700: Saturday 8:20
2011122500: Sunday 8:20
2012122200: Saturday 8:30
2015121900: Saturday 8:25
2015122600: Saturday 8:25


EAI_GAIN Error in Logfile

found these in my log file:

telegram.0
2020-04-29 19:51:10.949
error
(2776) RequestError: Error: getaddrinfo EAI_AGAIN api.telegram.org     at new RequestError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:14:15)     at Request.plumbing.callback (/opt/

telegram.0
2020-04-29 19:51:10.944
error
(2776) uncaught exception: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org

Anything I can do about this?

Check your DNS settings and name lookup for domain names. Ethos error says that telegram.org can not be looked up into an IP

thanks .. no more of these for a while .. maybe my internet was problematic


RouteParser is not always present

When the RoutingMiddleware is automatically instantiated by the RouteRunner because routing was not performed:
https://github.com/slimphp/Slim/blob/4.x/Slim/Routing/RouteRunner.php#L72
It calls performRouting but that means it doesn't append the RouteParser via this call since process is never called:
https://github.com/slimphp/Slim/blob/4.x/Slim/Middleware/RoutingMiddleware.php#L58
We need to fix this by moving that line into the performRouting method.

@adriansuter I tried reaching out to you via Slack but it doesn't look like you've been active. Is there a way for me to direct message you somewhere else? I have something to ask you.


Kill running terminal processes at restart / close

When installing extensions and restarting VS Code, the running terminal processes becoming detached and running in background instead, even when just closing terminal.

Is it possible instead to kill all running (master) processes automatically?

What's your OS? If it's mac or linux could you test on the latest version of Insiders? Might be fixed with https://github.com/Microsoft/vscode/issues/56217

Oh, well, no, its Windows 10, but i can boot linux tomorrow and check this - thanks 👍

Ah for Windows we have changes which we hope to solve as part of this issue https://github.com/Microsoft/vscode/issues/45693, stay tuned 😃


fix(Token): fixed cluster token validation

Q
A

Bug fix?
yes

New feature?
no

API breaks?
no

Deprecations?
no

Related tickets
-

License
Apache 2.0

What's in this PR?

Fixed the JWT token storing and thus validation with the new go-jose JWT implementation.
Why?

The cluster tokens are non-expiring, but they were stored with an explicit expiration set to 0 explicit time (0001-01-01T00:00:00Z), because at one point where we converted between non-pointer to pointer expiration the address of the zero value time was taken instead of setting expiration to nil.
Example: (token saved with no expiration/zero time value)
{
  "token": {
    "expiresAt": "0001-01-01T00:00:00Z",
    "id": "c81ee9e4-e925-40b6-8034-9e8b7d0b79b8",
    "name": "clusters/1/14",
    "value": "eyJhbGciOiJIUzI1NiJ9.eyJhdWQiOlsiaHR0cHM6Ly9waXBlbGluZS5iYW56YWljbG91ZC5jb20iXSwiaWF0IjoxNjA0NTk4NzcxLCJpc3MiOiJodHRwczovL2JhbnphaWNsb3VkLmNvbS8iLCJqdGkiOiJjODFlZTllNC1lOTI1LTQwYjYtODAzNC05ZThiN2QwYjc5YjgiLCJzY29wZSI6ImFwaTppbnZva2UiLCJzdWIiOiJjbHVzdGVycy8xLzE0IiwidGV4dCI6ImNsdXN0ZXJzLzEvMTQiLCJ0eXBlIjoiY2x1c3RlciJ9.you_thought_so"
  }
}

Additional context

Among long term design ideas up for debate:

we should use time pointers everywhere or no time pointers at all, but converting between values and pointers is always erroneous, especially when the zero value has a special meaning and not equals the semantic of any other value.
we should consider updating the Vault auth lookup token parsing to handle zero time value as well as nil value (it's a pointer there), because I think this is a somewhat "common" serialization issue.

Checklist

[X] Implementation tested (with at least one cloud provider)
~Code meets the Developer Guide
~OpenAPI and Postman files updated (if needed)~
~User guide and development docs updated (if needed)~
~Related Helm chart(s) updated (if needed)

I'm going to add some unit tests while I'm waiting for the CI, because the current ones didn't catch this issue, even though they easily should have.


Updated Report-name Regex

I got this issue in the email thread, no jira Ticket:

The report names with "(" threw SQL injection error, I identified the mistake to be incorrect Regex, I am not sure how this worked in the past.
Still testing this.
cc: @edcable  @bharathc27

I got this issue in the email thread

Which email thread? :smile:

no jira Ticket:

It would be great to create a JIRA issue, describing the problem, with the error message. With text, so that it's searchable, instead of an image. It helps when we look for it again in the future, when a user reports the same error on the mailing list later.

I am not sure how this worked in the past.

It's possible that it hasn't worked in a long time and was just broken... :sweat_smile:
Would it be possible to add a simple integration test for this?

My bad :P
Let me quickly make a  jira ticket for this explaining the entire issue.

+1 for the integration test as well.

@edcable  @bharathc27  I have tested this for not SQL errors anymore, will you like to test this locally with the community app? If that looks we can add an integration test and merge this?

@bharathc27 have you had a chance to test yet?

@francisguchie are you able to test this locally from your side? @thesmallstar @vorburger is it possible to merge this so @bharathc27 could test against fineract.dev - he doesn't have a local build of Fineract running on his current device.

@edcable  Let me try to setup community app locally (Somehow it is not working), I will give an update soon. It will be better if we test and merge this.
@vorburger  just an idea, can we do something to host a particular branch/PR whenever required online? It will be so much handy to test the PRs that way, should I make an issue for this?

@thesmallstar @vorburger is it possible to merge this so @bharathc27 could test against fineract.dev

sure, let's just merge this as-is now. @thesmallstar you can add the IT in a follow-up PR.

@edcable Let me try to setup community app locally (Somehow it is not working), I will give an update soon. It will be better if we test and merge this.

@thesmallstar if you have some JS issue, just FYI you could technically use https://cui.fineract.dev with a baseApiUrl to localhost. But cui.fineract.dev is not auto updated - watch https://github.com/openMF/community-app/issues/3309 about that.
@vorburger just an idea, can we do something to host a particular branch/PR whenever required online? It will be so much handy to test the PRs that way, should I make an issue for this?
That's... not that easy. I thought about it as well. But running a server instance costs. Running a server for every open PR is... non-negligeable. We sure could have some Bot, with some command, with some timeout that "tears down" per-PR servers, but.. this is a amount of work I don't have the time for to spend, unfortunately.
However, I think it's acceptable to sometimes merge PRs so that people can test things on demo.fineract.dev. If things are broken, then follow-up PRs can add further fixes. (The clean thing to do in theory would actually a PR with a git revert and then the proper fix.)


appengine local package error

go version 1.7
dlv version 0.11.0
given package models inside root appengine directory:
import "models"
Appengine compiles this successfully. However delve cannot find package because root is not added to GOPATH. But, I don't want to put models inside root/src/. How can I work around this?

I'm not familiar with the appengine workflow, does appengine build an executable? If it does and you can figure out a way to pass compiler flags to it then build with -gcflags='-N -l' then debug the executable with dlv exec ./filename.

This seems related to Google App Engine issue 35901233

Closing, no feedback and it doesn't look like there's anything we could do about this.


[ci] fix broken tests

found in https://buildkite.com/vllm/ci/builds/10303#01939a57-bf9d-4e2f-8d32-384b5c5077e2

this should fix the

list index out of range

error in https://buildkite.com/vllm/ci/builds/10303#01939a57-bf9d-4e2f-8d32-384b5c5077e2 .
for

ValueError: Multi-Step not supported for attention backend: NO_ATTENTION. Set VLLM_ATTENTION_BACKEND to a value from ['FLASH_ATTN', 'ROCM_FLASH', 'FLASHINFER'].

I have pinged @tlrmchlsmth , it should be https://github.com/vllm-project/vllm/pull/10705


Custom webpack

What this PR does / why we need it:
Hey all, I ran create-plugin update in one of our plugins that had a webpack.config.ts in its root with some plugin-specific loaders. The script overwrote them to use the ./config/webpack.config.ts, which made some build steps in the CI fail.
I'm not sure if this is the best way to do it, but I tried to add a check that, if the plugin already has a webpack.config.ts file, it will use that file in build and dev scripts.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@idastambuk we really appreciate you looking into a fix for this. It's a known issue that was reported here. However due to how the update command currently operates and, as you've witnessed, breaks things in multiple ways we've decided to rewrite it so it's smarter when it comes to making changes.
Given we already have a way forward that be implemented soon and will solve this issue (along with the others listed in the epic) I'm going to go ahead and close this.


Gathering: Report DGs and errors

report the DG for individual legs and put information into the json file

We now plan to extract the DDG and MBAR error from each leg.


Use std::filesystem instead of windows API in Orbiter core

This is a follow-up to PR #374 which failed to build after the C++ version was demoted.
It is the same as the original PR with the "auto &&" (abbreviated function template?) replaced with "std::function" parameters.

Does not compile on visual studio 2022 64 bits
ifstream ulf(entry); in psys.cpp
Gravité	Code	Description	Projet	Fichier	Ligne	État de la suppression	Détails
Erreur (active)	E0289	aucune instance du constructeur "std::basic_ifstream<_Elem, _Traits>::basic_ifstream [avec _Elem=char, _Traits=std::char_traits]" ne correspond à la liste d'arguments	Orbiter.exe (Modules\Server\Orbiter.exe) - C:\orbisource2\orbiter\Src\Orbiter\Psys.cpp	233

That's odd. I did test compile it on VS2019 before merge (x86). Have you tried x86 ?

Couldn't find a single compiler that accepts this on compiler explorer, so it must work only on VS2019 :sadface:
Managed to get clang/gcc to compile it by replacing the offending line with this :
ifstream ulf(entry.path());
@spacex15 : since I cannot test it (using VS2019 here), can you confirm it works on your side so I can push the fix?
Thanks

Couldn't find a single compiler that accepts this on compiler explorer, so it must work only on VS2019 :sadface:

@TheGondos https://godbolt.org/z/jqdKen91d
Your fix of adding .path() after entry is correct.

@thegondos I confirm the fix works on visual studio 2022
thanks


ESP needs a reboot after first OTA flash

This is a known issue with the ESP8266 - the workaround is to ensure the ESP8266 is reset / power cycled after the initial serial flash.
https://github.com/esp8266/Arduino/issues/2876
https://github.com/esp8266/Arduino/issues/1722
https://github.com/esp8266/Arduino/issues/2478
@brownjohnf @mccollam please can you try the work around above and see if the problem persists.

 Not sure when I'll have a minute though.


npm package is not up to date - firefox redirect bug

please merge/update the latest firefox fix for npm:
          if (e.preventDefault) {
            // stops the browser from redirecting.
            e.preventDefault();
          }

Published the new version just now! https://github.com/james2doyle/vue-drag-and-drop/releases/tag/2.1.0


Add html demo for async generators.

After having written a section for the wiki, I propose this PR as a simple demo for async generators and for-on loops.

Neat!

Addressed your issues.


promtail_config_expand_env variable is wrong by default

In defaults/main.yml variable promtail_config_expand_env have a string type. And condition in templates/service.j2 have no bool filter. As result with the default vars option -config.expand-env will be true. When promtail_config_expand_env is false without quotes, option -config.expand-env will be false.
Also templating -config.expand-env={{ "true" if promtail_config_expand_env else "false" }} can be simplified to -config.expand-env={{ promtail_config_expand_env | string }}

Thank you for reporting this - if you send a pull request, I'd be happy to release a fixed version with your changes


ensure that first set of footnotes are correctly formatted

This issue will be closed when footnotes are correctly formatted (per the discussion in #6).

@jpapagelis24 when you have a chance can you please review this commit and confirm that I've correctly reformatted the footnotes from chapters 1 and 2? Thanks in advance, Nick
https://github.com/STAT325-S24/HistoryAmherstCollege/commit/1ffde7937db31461addf186428f44e3a00751905

Looks good for chapters 1 and 2!


Use same chart multiple times in a page

I'm not sure if this is the best place to ask this question, but I am wondering if the same chart can be used multiple times on the page (i.e., having multiple canvas)? In the documentation, the chart is initiated by var ctx = document.getElementById("myChart").getContext("2d");.
Is there anyway to use a class? I tried document.getElementsByClassName, but that results in an error.

viado


image upload path

How can I upload the pics in path format just like this "Movie/PrimaryImage/{TenantId}" or  "Movie/PrimaryImage/{DateTime.Now}"

Also how can I change the image size？

Unless you write your own ImageUploadBehavior, you can't do such things, only supported parameters are entity id and some random file code. Take ImageUploadBehavior as sample and write your own if you are desperate.
ImageUploadEditor has some attributes to control image size. ScaleWidth, ScaleHeight, ThumbSizes etc. It's pretty well documented.


Optimizer

Adding the optimizer code to SeaCloudsPlatform

SeaClouds » SeaCloudsPlatform #126 SUCCESS
This pull request looks good
(what's this?)

thanks @perezp!


User agent is not being passed to chromium

For some reason chromium ignores user agent command line command. This might be the reason behind #64.

Appears to work fine after additional testing


The behavior of EarlyStopping is not the same between 0.7.5 with 0.7.3

🐛 Bug

The behavior of EarlyStopping is not the same between 0.7.5 with 0.7.3, If i set patience=1, 0.7.3 will print two epoch when the second is worse than the first, but 0.7.5 will just print the first which is not consistent with the description of patience parameter
To Reproduce

Code sample
early_stop_callback = EarlyStopping(monitor='valid_roc_auc', patience=0, mode='max', verbose=True)
# Instance Model, Trainer and train model
model = PlantModel(hparams)
trainer = pl.Trainer(gpus=[hparams.gpus],
                     max_epochs=hparams.max_epochs,
                     early_stop_callback=early_stop_callback,
                     progress_bar_refresh_rate=0,
                     num_sanity_val_steps=0,
                     profiler=True,
                     gradient_clip_val=hparams.gradient_clip_val)
trainer.fit(model)
print(trainer.early_stop_callback.wait)

Expected behavior

Environment

CUDA:
- GPU:
- GeForce RTX 2080 Ti
- GeForce RTX 2080 Ti
- GeForce RTX 2080 Ti
- GeForce RTX 2080 Ti
- available:         True
- version:           10.1
Packages:
- numpy:             1.18.1
- pyTorch_debug:     False
- pyTorch_version:   1.4.0
- pytorch-lightning: 0.7.5
- tensorboard:       2.2.1
- tqdm:              4.42.1
System:
- OS:                Linux
- architecture:
- 64bit
-
- processor:         x86_64
- python:            3.7.6
- version:           #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 2020

Additional context

@jeremyjordan

yes i believe this is the same issue reported in this comment and will be addressed in #1504

reported

Yes, exactly the same problem, It seems the only way to use 0.7.5 is to change the source code my self😢


Changed conditions of running GitHub actions

The GitHub actions were running everytime a new commit was made to the repo, but that wasn't needed. For example, we don't need to try to create a new docker image if the libraries didn't change, same to build the whole site after a change in the README.md.

Awesome!


perf: optimize style searching

Please read and mark the following check list before creating a pull request:

[x] I read and followed the CONTRIBUTING.md guide.
[x] I read and followed the New Feature Checklist guide.

Short description of what this resolves:
We don't need filter here since it will return all items matching the query
while we actually need only the first one. This change reduces average
time of the execution from ~2.00ms to ~0.15ms.
before:

after:

@kovetskiy nice catch! Just curious - can we use Array.prototype.find here? Less changes, same perf improvements

@artyorsh you are right, find() can be used here and it should be even faster (still showing 0.15 for me though).
I've force-pushed.


fix subchannel test in VTB

remove not needed parameter from input file
regold if needed

Closed by https://github.com/idaholab/virtual_test_bed/pull/258


feat(docs): show a warning in v1 docs

Description
closes #6980

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
[ ] Ideally, include a test that fails without this PR but passes with it.
[ ] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

[ ] Run the tests with pnpm test:ci.

Documentation

[ ] If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

[ ] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

LGTM! Thank you!


DateRangePicker Singe Date Selection Issues

Hello,
Really appreciate your work on this awesome project!
I'm having issues selecting a single date with the daterangepicker. The first issue is with the UI as shown below. When trying to select a single date the first time, the selection simply disappears. However, the second time I select a single date, it stays.
https://user-images.githubusercontent.com/81941044/155823051-aebb582d-e2f4-44bd-a8d9-7200f4520c81.mov
The second issue is triggering a callback with a single date selection. Can this be done? I was hoping the callback value would be something along the lines of ["selected_start_date", maxDate], but a single selection does not appear to trigger the callback.
Thanks in advance for any help.

Hi @bigmike36c, Thanks for reporting this issue. I agree with your comment about the behaviour and I have corrected that (will be released in 0.6.0).
Regarding your second issue, can you please briefly explain your process? How will you use it if single date selection were to trigger a callback.

Thanks for correcting this so quickly!
In my mind, if a user only selects a single date, then the user expects the date range to extend from the start date to the maximum date available.
The code snippet below is essentially how I've been handling this with the default dcc.DatePickerRange. If the callback is triggered with only one date selected (either start or end), the other date is simply set to an empty string in the callback. I then convert the empty string to the minimum or maximum date in the dataframe.
start_date = start_date or df["datetime"].min()
end_date = end_date or df["datetime"].max()

Since the dmc.DateRangePicker only lets you select the start date on its own, I think it would make the most sense for the callback to receive ["selected_start_date", maxDate]. If the maxDate parameter was not set, it could be replaced with an empty string or None.

Okay got it.
I can think about partial callback where in you at least get one date which is selected (keeping in mind backwards compatibility).
But I don't think we can do

callback to receive ["selected_start_date", maxDate].
It makes the date range picker less intuitive as to what's in the value is not what's displayed, etc.

Makes sense to me. Could the callback just trigger with "selected_date" as a string instead of a list? This would make it easy to handle both single date and range selections in the callback logic with the isinstance() function.

Ability to select single date won't be supported in dmc.DateRangePicker, for such purposes please use two date pickers.


Fails to build with Rust > 1.79

Hi,
Could you bump the time crate to at least 0.3.36 to fix the build with Rust-1.80?
Currently, our package is broken because of this.
Thanks!

Seconded. Workaround for me was to cargo install uair, without --locked, which is hardly ideal.
Thanks @metent !

Sorry, I've been away for while. I didn't expect things to break so soon. I'll release a fix asap.

Fixed with release v0.6.2.


Support collectibles

Implement alternative so we don't depend on OpenSea

I think in a first version it would even be fine to depend on open sea, this would allow us to switch this out over time ;)


Dont work ?

Game name: (please, specify the game name)
Engine version: (specify engine version, if known)
Platform: (specify platform, if known)
Error message: Could not load file or assembly 'HLSLccWrapper, Version=1.0.7610.22677, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
Stack trace:    at uTinyRipperGUI.Exporters.ShaderHLSLccExporter.Export(ShaderWriter writer, ShaderSubProgram& subProgram)
at uTinyRipper.Classes.Shaders.ShaderSubProgram.Export(ShaderWriter writer, ShaderType type)
at uTinyRipper.Classes.Shaders.SerializedSubProgram.Export(ShaderWriter writer, ShaderType type, Boolean isTier)
at uTinyRipper.Classes.Shaders.SerializedProgram.Export(ShaderWriter writer, ShaderType type)
at uTinyRipper.Classes.Shaders.SerializedPass.Export(ShaderWriter writer)
at uTinyRipper.Classes.Shaders.SerializedSubShader.Export(ShaderWriter writer)
at uTinyRipper.Classes.Shaders.SerializedShader.Export(ShaderWriter writer)
at uTinyRipper.Classes.Shader.ExportBinary(IExportContainer container, Stream stream, Func3 exporterInstantiator)    at uTinyRipperGUI.Exporters.ShaderAssetExporter.Export(IExportContainer container, Object asset, String path)    at uTinyRipper.Project.AssetExportCollection.Export(ProjectAssetContainer container, String dirPath)    at uTinyRipper.Converters.ProjectExporter.Export(String path, GameCollection fileCollection, IEnumerable1 files, ExportOptions options)
at uTinyRipper.GameStructure.Export(String exportPath, Func`2 filter)
at uTinyRipperGUI.MainWindow.ExportFiles(Object data)

uTinyRipper has been abandoned, but you can try my AssetRipper fork. In the event that AssetRipper encounters issues while ripping your files, feel free to post an issue on that repository.
AssetRipper is actively being developed with the intent to recover games as best as possible. I encourage you to help out if you're able and willing. Code contributions can be submitted via pull requests.
If you like the work I've done and want to see it continue, please consider sponsoring me. It really does help with development. These are some of the notable things I've implemented since taking over development:

2020+ support
APK, XAPK, and IPA reading with SharpZipLib
Dummy shaders (so everything isn't pink when you open the project)
IL2Cpp support via an integration of Cpp2IL
Better game platform support
Full script decompilation with the ILSpy decompiler
Cross-platform support
Multiple configuration options
Numerous performance improvements

Links:

Patreon


ntr:normal movement along microtubules

https://curation.pombase.org/pombe/curs/f2b0ffda72370b22/ro
normal protein transport on microtubule tip
normal protein transport by microtubule polymerization
situation where the rate of protein transport on a polymerising microtubule tip is the same as wild type
https://github.com/geneontology/go-ontology/issues/12822

Actually, I don't get this now.
If tea1 is a the  microtubule + end, and the microtubule is polymerising from the +end, how can tea1 stay at the tip when new tubulin is being added. There must be some movement of tea1  to keep it at the end?

ntr normal localisation to microtubule end during mitotic interphase
ntr normal localisation to microtubule + end during mitotic interphase

ignore
ntr decreased maintenance of protein localization to cell cortex of cell tip
These observations suggest that tea1(􏰅200)p generally disengages from the microtubu- lar tips but either fails to become associated with the cell end cortex or persists there for only a short time.
(at this point unclear whether establishment, maintenence or both)

Jacky requested
Long cytoplasmic microtubules curved around cell end during mitotic interphase
situation during mitotic interphase where microtubules fail to stop growing when they reach the cell tip and continue to grow curving around the cell end
(didn't we once decide that all long interphase microtubules curved around the cell tip?)

Jacky requested
normal protein transport on microtubule tip
situation where the rate of protein transport on a polymerising microtubule tip is the same as wild type
which is what I was trying to do above....
@jvhayles
does tea1 move both along the microtubule, and is transported on the tip then?

I think there is also a situation where interphase microtubules( bundles) are long and curved but look like a bow because they stop at the cell tips This is different to the hook like phenotype where they are not so curved except they continue round the cell end.   I think it happens when a single microtubule bundle is formed on one side of the cell.  You can see this in Verde Mata and Nurse JCB vol131 1995 pp1529-1538  Fig 9 Fulvia says in this paper that tea1 Mts are normal but Juan showed that sometimes they curved around the end. .  I feel that there is a difference between the two descriptions, for the  long curved microtubules I think the cell is curved because the microtubule bundle is curved and the cell tip is organised where the MT stops i.e. at the cell end whereas in tea1 some of the microtubule bundles go pass the cell  tip .  I hope this makes sense its a bit rambly
Jacky
From: Val Wood <notifications<EMAIL_ADDRESS>Reply-To: pombase/fypo <reply<EMAIL_ADDRESS>Date: Wednesday, 23 November 2016 at 19:08
To: pombase/fypo <fypo<EMAIL_ADDRESS>Subject: Re: [pombase/fypo] ntr:normal movement along microtubules (#2896)
Jacky requested
Long cytoplasmic microtubules curved around cell end during mitotic interphase
situation during mitotic interphase where microtubules fail to stop growing when they reach the cell tip and continue to grow curving around the cell end
(didn't we once decide that all long interphase microtubules curved around the cell tip?)

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/pombase/fypo/issues/2896#issuecomment-262604870, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANVVaEEVWTullglHMdDEJNazKsjR-P_Bks5rBI9LgaJpZM4K67ju.
The Francis Crick Institute Limited is a registered charity in England and Wales no. 1140062 and a company registered in England and Wales no. 06885462, with its registered office at 215 Euston Road, London NW1 2BE.

People have looked at this but I don't know the answer. But I agree it does seem that it would have to keep moving as tubulin subunits are added  Claude Antony may have done something about this with mal3 at the MT end
Jacky
From: Val Wood <notifications<EMAIL_ADDRESS>Reply-To: pombase/fypo <reply<EMAIL_ADDRESS>Date: Wednesday, 23 November 2016 at 18:49
To: pombase/fypo <fypo<EMAIL_ADDRESS>Subject: Re: [pombase/fypo] ntr:normal movement along microtubules (#2896)
Actually, I don't get this now.
If tea1 is a the microtubule + end, and the microtubule is polymerising from the +end, how can tea1 stay at the tip when new tubulin is being added. There must be some movement of tea1 to keep it at the end?

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/pombase/fypo/issues/2896#issuecomment-262600302, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANVVaAPAg77PwyhCIDQqiGc8PAub-DIXks5rBIq3gaJpZM4K67ju.
The Francis Crick Institute Limited is a registered charity in England and Wales no. 1140062 and a company registered in England and Wales no. 06885462, with its registered office at 215 Euston Road, London NW1 2BE.

That makes sense.
I'll put this in a FYPO ticket.
Do you know which papers/alleles are which phenotype? (we can check at
some point)
Val
FYPO_ID(FYPO:0000055 - long microtubules) for All Alleles    32
FYPO_ID(FYPO:0004862 - curved microtubules) for All Alleles 13
FYPO_ID(FYPO:0004511 - long curved cytoplasmic microtubules) for All
Alleles 6
Some of these are probably long spindle microtubules
( FYPO_ID(FYPO:0000055 - long microtubules) for All Alleles )NOT(
FYPO_ID(FYPO:0003787 - long mitotic spindle microtubules protruding
beyond spindle pole body) for All Alleles ) 26
Are all curved microtubules long? or not necessarily?
Val
On 24/11/2016 10:29, Jacky Hayles wrote:

I think there is also a situation where interphase microtubules(
bundles) are long and curved but look like a bow because they stop at
the cell tips This is different to the hook like phenotype where they
are not so curved except they continue round the cell end. I think it
happens when a single microtubule bundle is formed on one side of the
cell. You can see this in Verde Mata and Nurse JCB vol131 1995
pp1529-1538 Fig 9 Fulvia says in this paper that tea1 Mts are normal
but Juan showed that sometimes they curved around the end. . I feel
that there is a difference between the two descriptions, for the long
curved microtubules I think the cell is curved because the microtubule
bundle is curved and the cell tip is organised where the MT stops i.e.
at the cell end whereas in tea1 some of the microtubule bundles go
pass the cell tip . I hope this makes sense its a bit rambly
Jacky
From: Val Wood <notifications<EMAIL_ADDRESS>Reply-To: pombase/fypo
<reply<EMAIL_ADDRESS>Date: Wednesday, 23 November 2016 at 19:08
To: pombase/fypo <fypo<EMAIL_ADDRESS>Subject: Re: [pombase/fypo] ntr:normal movement along microtubules (#2896)
Jacky requested
Long cytoplasmic microtubules curved around cell end during mitotic
interphase
situation during mitotic interphase where microtubules fail to stop
growing when they reach the cell tip and continue to grow curving
around the cell end
(didn't we once decide that all long interphase microtubules curved
around the cell tip?)

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on
GitHubhttps://github.com/pombase/fypo/issues/2896#issuecomment-262604870,
or mute the
threadhttps://github.com/notifications/unsubscribe-auth/ANVVaEEVWTullglHMdDEJNazKsjR-P_Bks5rBI9LgaJpZM4K67ju.
The Francis Crick Institute Limited is a registered charity in England
and Wales no. 1140062 and a company registered in England and Wales
no. 06885462, with its registered office at 215 Euston Road, London
NW1 2BE.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pombase/fypo/issues/2896#issuecomment-262742853,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHBLKEIuGLGvsReBnslCXivz_NlrleTIks5rBWchgaJpZM4K67ju.

--
Cambridge University
PomBase http://www.pombase.org/
Cambridge Systems Biology Centre http://www.sysbiol.cam.ac.uk/Investigators/val-wood

Yes tea1 does only move on the tips of microtubules.  I don't know why I added along microtubules for Fig4A because here they just show that the movement of tea1delta200 is the same as tea1+ so in fact it doesn't need a new term.  I was thinking of its transport on microtubules but in fact this only confuses the idea of it moving with growing microtubules as opposed travelling along microtubules
Sorry
Jacky
From: Val Wood <notifications<EMAIL_ADDRESS>Reply-To: pombase/fypo <reply<EMAIL_ADDRESS>Date: Wednesday, 23 November 2016 at 18:47
To: pombase/fypo <fypo<EMAIL_ADDRESS>Subject: [pombase/fypo] ntr:normal movement along microtubules (#2896)
https://curation.pombase.org/pombe/curs/f2b0ffda72370b22/ro
Jacky requested
normal movement along microtubules
situation where movement of a protein along microtubules is the same as wild type
but, as tea1 does not move along the microtubules but moves because it is at the tip and the tips grow, I wonder if it should be
normal protein transport by microtubule polymerization
Anyone have a suggestion? @jvhayles
geneontology/go-ontology#12822https://github.com/geneontology/go-ontology/issues/12822

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/pombase/fypo/issues/2896, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANVVaFR5jhZihwdRlvKNeIJVz5K-67w3ks5rBIpZgaJpZM4K67ju.
The Francis Crick Institute Limited is a registered charity in England and Wales no. 1140062 and a company registered in England and Wales no. 06885462, with its registered office at 215 Euston Road, London NW1 2BE.

So it seems that tea2 does actually transport tip1
https://curation.pombase.org/pombe/curs/ce1fc9c90e999884
I thought that the phenotypes for tea1/tea1 in earlier papers look
similar/identical
Are these different conclusions from the same phenotypes?
val
On 24/11/2016 10:38, Jacky Hayles wrote:

People have looked at this but I don't know the answer. But I agree it
does seem that it would have to keep moving as tubulin subunits are
added Claude Antony may have done something about this with mal3 at
the MT end
Jacky
From: Val Wood <notifications<EMAIL_ADDRESS>Reply-To: pombase/fypo
<reply<EMAIL_ADDRESS>Date: Wednesday, 23 November 2016 at 18:49
To: pombase/fypo <fypo<EMAIL_ADDRESS>Subject: Re: [pombase/fypo] ntr:normal movement along microtubules (#2896)
Actually, I don't get this now.
If tea1 is a the microtubule + end, and the microtubule is
polymerising from the +end, how can tea1 stay at the tip when new
tubulin is being added. There must be some movement of tea1 to keep it
at the end?

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on
GitHubhttps://github.com/pombase/fypo/issues/2896#issuecomment-262600302,
or mute the
threadhttps://github.com/notifications/unsubscribe-auth/ANVVaAPAg77PwyhCIDQqiGc8PAub-DIXks5rBIq3gaJpZM4K67ju.
The Francis Crick Institute Limited is a registered charity in England
and Wales no. 1140062 and a company registered in England and Wales
no. 06885462, with its registered office at 215 Euston Road, London
NW1 2BE.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pombase/fypo/issues/2896#issuecomment-262744627,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHBLKLo4ZAjEbC5njJ6kuBezYScbRA6wks5rBWkSgaJpZM4K67ju.

--
Cambridge University
PomBase http://www.pombase.org/
Cambridge Systems Biology Centre http://www.sysbiol.cam.ac.uk/Investigators/val-wood

Could one of you summarize what new term(s) I should add? I got a bit lost reading all the comments ...
Is it normal GO:0099110 (microtubule polymerization based protein transport to cell tip cortex, the term added for https://github.com/geneontology/go-ontology/issues/12822)?

for starters its
ntr normal localisation to microtubule end during mitotic interphase
ntr normal localisation to microtubule + end during mitotic interphase
ntr decreased protein localization to cell cortex of cell tip
(only one of that batch was  abandoned)

then normal protein transport on microtubule tip

ntr normal localisation to microtubule end during mitotic interphase
ntr normal localisation to microtubule + end during mitotic interphase

protein localization?

whopps yes will fix that

Hi @jvhayles
I had another look at these papers:
Conclusions of PMID:11018050
In the absence of Tea2p, Tea1p localizes along the short cytoplasmic microtubules characteristic of tea2delta cells. Therefore, although Tea1p has an affinity for microtubules in the absence of Tea2p, proper localization of Tea1p to the cell tip requires Tea2p. One possibility is that Tea2p transports Tea1p along microtubules and deposits it at the cell tip. A second possibility is that Tea1p uses an- other microtubule-mediated mechanism to get to the tip of the cell, and the absence of a normal array of cytoplasmic microtubules in tea2delta cells results in the mislocalization of Tea1p.
So I don't think this paper says that tea1 is transported on the tip.
It says
Tea2 is not required for localization to microtubules
Tea2 is required for localization to the tip.
It doesn't say anything about the mechanism from this paper, and probably stick with the localization phenotypes?
The later paper on tea2/tip1 appears to have similar phenotypes  to the Tea2/tea1
but also looks at movement along microtubule and concludes that
Tea2 transports tip1 to the tip.
Is there any evidence that makes transport of tea1 actually on the tip by polymerization (as opposed to tea2 keeping it at the tip by its motor activity) a possibility.
Otherwise, we might have created a GO term for something which is not mechanistically possible....

did you mean tea1/tea2
On 24 Nov 2016, at 12:16, Val Wood <notifications<EMAIL_ADDRESS>wrote:
So it seems that tea2 does actually transport tip1
https://curation.pombase.org/pombe/curs/ce1fc9c90e999884
I thought that the phenotypes for tea1/tea1 in earlier papers look
similar/identical
Are these different conclusions from the same phenotypes?
val
On 24/11/2016 10:38, Jacky Hayles wrote:

People have looked at this but I don't know the answer. But I agree it
does seem that it would have to keep moving as tubulin subunits are
added Claude Antony may have done something about this with mal3 at
the MT end
Jacky
From: Val Wood <notifications@github.commailto:notifications<EMAIL_ADDRESS>Reply-To: pombase/fypo
<reply@reply.github.commailto:reply<EMAIL_ADDRESS>Date: Wednesday, 23 November 2016 at 18:49
To: pombase/fypo <fypo@noreply.github.commailto:fypo<EMAIL_ADDRESS>Subject: Re: [pombase/fypo] ntr:normal movement along microtubules (#2896)
Actually, I don't get this now.
If tea1 is a the microtubule + end, and the microtubule is
polymerising from the +end, how can tea1 stay at the tip when new
tubulin is being added. There must be some movement of tea1 to keep it
at the end?

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on
GitHubhttps://github.com/pombase/fypo/issues/2896#issuecomment-262600302,
or mute the
threadhttps://github.com/notifications/unsubscribe-auth/ANVVaAPAg77PwyhCIDQqiGc8PAub-DIXks5rBIq3gaJpZM4K67ju.
The Francis Crick Institute Limited is a registered charity in England
and Wales no. 1140062 and a company registered in England and Wales
no. 06885462, with its registered office at 215 Euston Road, London
NW1 2BE.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pombase/fypo/issues/2896#issuecomment-262744627,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHBLKLo4ZAjEbC5njJ6kuBezYScbRA6wks5rBWkSgaJpZM4K67ju.

--
Cambridge University
PomBase http://www.pombase.org/
Cambridge Systems Biology Centre http://www.sysbiol.cam.ac.uk/Investigators/val-wood
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/pombase/fypo/issues/2896#issuecomment-262763287, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANVVaLVj7MBGRXDwmUlQWCNIoyX6Bn8jks5rBYAjgaJpZM4K67ju.
The Francis Crick Institute Limited is a registered charity in England and Wales no. 1140062 and a company registered in England and Wales no. 06885462, with its registered office at 215 Euston Road, London NW1 2BE.

Both...
Why do we think that  the motor activity of tea2 transports tip1 to the microtubule tips
But
tea2 is involved in the movement of tea1  on the microtubule tips
Presumably the mechanism for the movement of Both tea1 and tip1 by tea2 is the same.
i.e.
tea2 transports both tip1 and tea1 along microtubules to the tip
the microtubules are polymerising, and so to keep them at the tip, they need to be moved by something?

Hi Val
I need to look at the papers but I can't do it now or this weekend. I'll do it on Monday is that OK
Jacky
Sent from my iPad
On 25 Nov 2016, at 12:16, Val Wood <notifications<EMAIL_ADDRESS>wrote:
Both...
Why do we think that the motor activity of tea2 transports tip1 to the microtubule tips
But
tea2 is involved in the movement of tea1 on the microtubule tips
Presumably the mechanism for the movement of Both tea1 and tip1 by tea2 is the same.
i.e.
tea2 transports both tip1 and tea1 along microtubules to the tip
the microtubules are polymerising, and so to keep them at the tip, they need to be moved by something?

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/pombase/fypo/issues/2896#issuecomment-262945127, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANVVaAbFR7EaqSQkJRdJE9SkfkTfg96yks5rBtGEgaJpZM4K67ju.
The Francis Crick Institute Limited is a registered charity in England and Wales no. 1140062 and a company registered in England and Wales no. 06885462, with its registered office at 215 Euston Road, London NW1 2BE.

Of course, No hurry!
I'm going to switch back to your cdc2 papers today anyway. I have 4 left...

This later one that I did before (the one with the switch and P-loop mutants)
PMID: 12894167
Browning H1, Hackney DD, Nurse P.
https://www.ncbi.nlm.nih.gov/pubmed/12894167?dopt=Abstract
Kinesins are microtubule-based motor proteins that transport cargo to specific locations within the cell. However, the mechanisms by which cargoes are directed to specific cellular locations have remained elusive. Here, we investigated the in vivo movement of the Schizosaccharomyces pombe kinesin Tea2 to establish how it is targeted to microtubule tips and cell ends. Tea2 is loaded onto microtubules in the middle of the cell, in close proximity to the nucleus, and then travels using its intrinsic motor activity primarily at the tips of polymerizing microtubules. The microtubule-associated protein Mal3, an EB1 homologue, is required for loading and/or processivity of Tea2 and this function can be substituted by human EB1. In addition, the cell-end marker Tea1 is required to anchor Tea2 to cell ends. Movement of Tea1 and the CLIP170 homologue Tip1 to cell ends is abolished in Tea2 rigor (ATPase) mutants. We propose that microtubule-based transport from the vicinity of the nucleus to cell ends can be precisely regulated, with Mal3 required for loading/processivity, Tea2 for movement and Tea1 for cell-end anchoring.
I  got from this  paper that Tea2 moves  Tea1 (i didn't do the GO terms though for some reason, only the phenotypes...I have done them now)

Hi Val
Is there any evidence that makes transport of tea1 actually on the tip by polymerization (as opposed to tea2 keeping it at the tip by its motor activity) a possibility.
In PMID1203477, they show that the rate of tea1GFP movement on microtubules is the same in wild type and tea2 Delta strains suggesting tea2 is not moving tea1GFP Fig2B, and they also show that tea1GFP co-localises with the growing microtubule ends.  I think the  cell tip localisation is indirect and the accumulation of tea1 in the vicinity of the nucleus is indirect because tea2  affects the length of the microtubules.  Does this help I'll also have a look at PMID 11018050
Jacky
From: Val Wood <notifications<EMAIL_ADDRESS>Reply-To: pombase/fypo <reply<EMAIL_ADDRESS>Date: Friday, 25 November 2016 at 11:40
To: pombase/fypo <fypo<EMAIL_ADDRESS>Cc: "Jacqueline.Hayles<EMAIL_ADDRESS><Jacqueline.Hayles<EMAIL_ADDRESS>Comment <comment<EMAIL_ADDRESS>Subject: Re: [pombase/fypo] ntr:normal movement along microtubules (#2896)
Hi @jvhayles
I had another look at these papers:
Conclusions of PMID:11018050
In the absence of Tea2p, Tea1p localizes along the short cytoplasmic microtubules characteristic of tea2delta cells. Therefore, although Tea1p has an affinity for microtubules in the absence of Tea2p, proper localization of Tea1p to the cell tip requires Tea2p. One possibility is that Tea2p transports Tea1p along microtubules and deposits it at the cell tip. A second possibility is that Tea1p uses an- other microtubule-mediated mechanism to get to the tip of the cell, and the absence of a normal array of cytoplasmic microtubules in tea2delta cells results in the mislocalization of Tea1p.
So I don't think this paper says that tea1 is transported on the tip.
It says
Tea2 is not required for localization to microtubules
Tea2 is required for localization to the tip.
It doesn't say anything about the mechanism from this paper, and probably stick with the localization phenotypes?
The later paper on tea2/tip1 appears to have similar phenotypes to the Tea2/tea1
but also looks at movement along microtubule and concludes that
Tea2 transports tip1 to the tip.
Is there any evidence that makes transport of tea1 actually on the tip by polymerization (as opposed to tea2 keeping it at the tip by its motor activity) a possibility.
Otherwise, we might have created a GO term for something which is not mechanistically possible....

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/pombase/fypo/issues/2896#issuecomment-262939114, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANVVaMle_mIo1SHReJg_XkMw_pHbpiOcks5rBskbgaJpZM4K67ju.
The Francis Crick Institute Limited is a registered charity in England and Wales no. 1140062 and a company registered in England and Wales no. 06885462, with its registered office at 215 Euston Road, London NW1 2BE.

'decreased protein localization to cell cortex of cell tip' was added for #2891 - it's FYPO:0005798
I've now added these:
normal protein localization to cytoplasmic microtubule plus-end during mitotic interphase FYPO:0005812
normal protein localization to microtubule end during mitotic interphase FYPO:0005813
If I'm reading all this correctly, what's still outstanding is the movement involving tea1, tea2, tip1, microtubule ends, etc. Whatever the correct wording and definition turn out to be for them, from this ticket and #2897 it looks like we should have 'normal' and 'abolished' terms. Is that correct?
I'm closing #2897 and will keep this ticket open for the mystery microtubule-based/related/whatever movement terms.
edit file: 85705a33c6973058513adaeb1cbffc0f932f4fba
release: f701ceddcb5be7069b0b51dd8744b5bc4d16e188

Latest thought on the movement-to-tip question, transferred from #2902:
Val says:
probably could do this arrangement for the other microtubule transport:
normal protein movement by microtubule-dependent transport to cell tip

normal protein movement along microtubule to cell tip
normal protein movement on microtubule tip to cell tip (probably)

Please stick one more comment here when you've decided what to use (the latest as above would be fine with me).

Further info & requests for less specific terms transferred from #2912:
"normal microtubule based movement of protein" to be superclass of normal protein movement along microtubule to cell tip and normal protein movement on microtubule tip to cell tip
also generic and both cell tip terms with 'abolished' and 'decreased' qualifiers

summary of what to add:
xp GO:0098840
normal protein transport along microtubule
abolished protein transport along microtubule
(decreased protein transport along microtubule is FYPO:0005494)
xp GO:new from https://github.com/geneontology/go-ontology/issues/12836
normal protein transport along microtubule to cell tip
abolished protein transport along microtubule to cell tip
decreased protein transport along microtubule to cell tip
xp GO:0099110 from https://github.com/geneontology/go-ontology/issues/12822
normal protein transport on microtubule tip to cell tip
abolished protein transport on microtubule tip to cell tip
decreased protein transport on microtubule tip to cell tip
all to have exact synonyms with 'movement' in place of 'transport'

added
normal protein transport along microtubule during vegetative growth FYPO:0005827
normal protein transport along microtubule to cell tip during vegetative growth FYPO:0005828
normal protein movement on microtubule tip to cell tip cortex during vegetative growth FYPO:0005829
abnormal protein transport along microtubule during vegetative growth FYPO:0005830
abnormal protein transport along microtubule to cell tip during vegetative growth FYPO:0005831
abnormal protein transport on microtubule tip to cell tip cortex during vegetative growth FYPO:0005832
decreased protein transport along microtubule to cell tip during vegetative growth FYPO:0005833
decreased protein transport on microtubule tip to cell tip cortex during vegetative growth FYPO:0005834
abolished protein transport along microtubule during vegetative growth FYPO:0005835
abolished protein transport along microtubule to cell tip during vegetative growth FYPO:0005836
abolished protein transport on microtubule tip to cell tip cortex during vegetative growth FYPO:0005837
I think that's everything for this and the linked tickets, so closing.
edit file: 0cae32187a9b7e3ab4814aa45a711690f6c2a847
release: f70fffa3731055d3715b8146b039bd01e45a71bf


Location contains edges

Fixes bug found by @mo-nathan during NEMF

coverage: 93.472%. remained the same
when pulling 3cbbb05b25517906809e023449cc893ba7c44048 on jdc-location-contains-edges
into 392afa9db57c97230cabdad43b6756987ecde85b on main.

Merging this immediately because it's a hot fix and a trivial change in the code.


mlc-ai-nightly -  Error installing

Hi Simon - saw your tweet about this library earlier and thought it was too cool, had to try it out.  I'm  having some issues with installing the two dependencies:
ERROR: Could not find a version that satisfies the requirement mlc-ai-nightly (from versions: none)
I'm on a M1 Pro.  I also tried going to the MLC site to see if maybe they updated the installation instructions - same problem. Wondering if anybody else has run into this yet?
Also unrelated - is this meant to be the successor to llm-llama-cpp?

I should probably ask this in MLC's Issues... moving it there

Did you manage to get it installed? I'm hitting the same

@christopherdbull Yes I did.  I was running an old version of MacOS (several updates behind, Ventura I think it was?).  After upgrading to Sonoma everything worked.  This was a problem I was running into with MLC and it's dependencies, not llm.


Some modules not compatible

The new orbital survey that requires 2 kerbals to operate does not receive life support even when supplies are linked through docks. Resource moving to those modules are also not possible,  also the green house modules have option for crew lights but cannot contain crew

Investigating, I'll see if I can push a quick fix for that soon.

Ive found a quick work around for it by going into settings, mods, life support settings and disable kerbals dying from lack of supplies this will disable the kerbals from dying inside of the pod but still seems to use resources so it all works out in the end


Remove username/password from Companion Pi

I'd like to be able to turn on/off power to the raspberry pi without having to re-enter username/password each time, but I can't see any way to remove the username/password, could anyone point me in the right direction?

What command are you using to do the shutdown?
This does setup passwordless sudo for shutdown, reboot and poweroff for the companion user

All good! I figured it out, in the sudo raspi-config menu, there's simply an auto-login option. Easy.


Fixes issues related to upgrading to the latest nightly

These changes aren't needed now, but they will be needed eventually to compile on the latest nightly when that is possible.

Needs rebase, but other than that LGTM.


Changelog?

The work on this has been great, have you considered running a changelog for users to keep track of?
Prior art is the js debug one https://github.com/microsoft/vscode-js-debug/blob/main/CHANGELOG.md
it offers visibility to changes (such as these https://github.com/microsoft/vscode-livepreview/pull/93) and makes it easy for users to scroll through/search change history.
I can understand if you don’t want to do this until you hit 1.0.0 though

Great idea! Thanks so much for the suggestion, made a PR for it. 😊


Enhancement: Swap default branch to master

Please check for duplicates or similar issues before creating this issue.
What is your suggestion, and why should it be implemented?
Change the master branch to master, because stable seems to only be updated occasionally or when the documentation needs updating. (That's what I can tell at least)

naw people will pull developmental changes and get mad that kade engine broke

prokube, the point is that people clone stable so they don't have a broken as hell kade engine as the base of their mod, thats why its the main branch

a


LaTeX Error: Option clash for package hyperref

First off, love both the concept and execution of showyourwork, this is so cool! 🎉  I'm very excited to get it working for LEGWORK 😄
When I try to run make I get the error
error: sywxml.sty:9: LaTeX Error: Option clash for package hyperref.

I'm only marginally LaTeX literate but I think this is probably because on the packages that I use in my tex file have conflicting options with something in showyourwork? I don't use hyperref directly but maybe it is in one of these ones:
I use the following packages if that helps
\usepackage{physics}
\usepackage[hang,flushmargin]{footmisc}
\usepackage{mathtools}
\usepackage{etoolbox}
\usepackage{fontawesome5}

It could also may be because I try doing thing like in Luger+19 with the links in equation environments? Here's the full preamble for the tex file in case you need more details!
\documentclass[twocolumn]{aastex63}
\received{\today}
\shorttitle{LEGWORK}
\graphicspath{{./}{figures/}}

\usepackage{physics}

% remove indents in footnotes
\usepackage[hang,flushmargin]{footmisc}

\newcommand{\todo}[1]{{\color{red}{[TODO: #1}]}}

% custom function for adding units
\makeatletter
\newcommand{\unit}[1]{%
    \,\mathrm{#1}\checknextarg}
\newcommand{\checknextarg}{\@ifnextchar\bgroup{\gobblenextarg}{}}
\newcommand{\gobblenextarg}[1]{\,\mathrm{#1}\@ifnextchar\bgroup{\gobblenextarg}{}}
\makeatother

\newcommand{\avg}[1]{\left\langle#1\right\rangle}

% LEGWORK stuff
\newcommand{\lw}{LEGWORK}
\newcommand{\lwColour}{SeaGreen}
\newcommand{\lwModURL}[1]{https://legwork.readthedocs.io/en/latest/modules.html\#module-legwork.#1}
\newcommand{\lwModLink}[1]{\href{https://legwork.readthedocs.io/en/latest/modules.html\#module-legwork.#1}{\color{\lwColour}{\texttt{#1}}}}
\newcommand{\lwFuncURL}[2]{https://legwork.readthedocs.io/en/latest/api/legwork.#1.#2.html\#legwork.#1.#2}

% icons and links
\newcommand{\docsIcon}{{\color{\lwColour}{\faFileCode}}}
\newcommand{\docsLink}[1]{\href{#1}{\docsIcon}}

\newcommand{\tutorialIcon}{{\color{\lwColour}{\faLaptopCode}}}
\newcommand{\tutorialLink}[1]{\href{#1}{\tutorialIcon}}

\newcommand{\notebookIcon}{{\color{\lwColour}{\faBook}}}
\newcommand{\notebookLink}[1]{\href{#1}{\notebookIcon}}

% add documentation links to equation environments
% Luger+19 inspired this!
\usepackage{mathtools, etoolbox, fontawesome5}
\newtagform{eqtag}[]{(}{)}

\renewenvironment{equation}[1]{%
    \ifstrempty{#1}{%
        \renewtagform{eqtag}[]{(}{)}%
    }{%
        \renewtagform{eqtag}[]{\docsLink{#1}\,(}{)}%
    }%
    \usetagform{eqtag}%
    \align%
    }{%
    \endalign%
    \renewtagform{eqtag}[]{(}{)}%
    \usetagform{eqtag}%
}

I have realised that it is because of aastex63 -- if I upgrade to aastex631 like in the example then it works just fine! 😄


Add in filtered search in Compare page

Adds in filtered search in compare page based on the selected facet items.

ping @vlandham