List of tools with relevance for genomic coordinates management and comparison, referring especially to annotated genes
List of tools
- Convert gtf to gff3
import tiktoken | |
import langdetect | |
T = tiktoken.get_encoding("o200k_base") | |
length_dict = {} | |
for i in range(T.n_vocab): | |
try: | |
length_dict[i] = len(T.decode([i])) | |
except: |
[Script Info] | |
Title: How AI Could Empower Any Business | Andrew Ng | TED | |
ScriptType: v4.00+ | |
WrapStyle: 0 | |
Collisions: Reverse | |
PlayResX: 384 | |
PlayResY: 288 | |
Timer: 100.0000 | |
ScaledBorderAndShadow: no |
# Copyright (C) 2018 Jameel Al-Aziz | |
# Modified for simplicification and use within CoreOS. | |
# | |
# Copyright (C) 2006-2016 Amazon.com, Inc. or its affiliates. | |
# All Rights Reserved. | |
# | |
# Licensed under the Apache License, Version 2.0 (the "License"). | |
# You may not use this file except in compliance with the License. | |
# A copy of the License is located at | |
# |
#!/bin/bash | |
if [[ $(id -u) -ne 0 ]]; then | |
echo "This script must be run as root" | |
exit 1 | |
fi | |
if [ -z $(pm list packages | grep com.snapchat.android) ]; then | |
echo "Snapchat not found" | |
exit 1 | |
fi |
This proof of concept uses ipvlan
feature of Linux to split up main
network interface into two in order to use one in a separate namespace
with jool-siit
performing CLAT translation.
This way, enabling CLAT is least intrusive to the default network namespace - no need to enable forwarding or touch firewall rules.
// | |
// MIT License | |
// | |
// Copyright (c) 2024 Derek Selander | |
// | |
// Permission is hereby granted, free of charge, to any person obtaining a copy | |
// of this software and associated documentation files (the "Software"), to deal | |
// in the Software without restriction, including without limitation the rights | |
// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
// copies of the Software, and to permit persons to whom the Software is |
See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions and generate verion and changelogs
<your-ticket-prefix> | |
# Subject Line | |
# ====================================================================== | |
# | |
# One line less than 72 characters in length. Generally focused on the | |
# "What" rather than the "Why". | |
# | |
# Format <tag>: <message> | |
# | |
# `tag`: can be either a defined list of tags like "Add", "Remove", |