| // | |
| // Lookup Tables for Marching Cubes | |
| // | |
| // These tables differ from the original paper (Marching Cubes: A High Resolution 3D Surface Construction Algorithm) | |
| // | |
| // The co-ordinate system has the more convenient properties: | |
| // | |
| // i = cube index [0, 7] | |
| // x = (i & 1) >> 0 | |
| // y = (i & 2) >> 1 |
| https://www.nseindia.com/corporates/datafiles/AN_NAV_LATEST_ANNOUNCED.csv | |
| https://www.nseindia.com/corporates/datafiles/BM_All_Forthcoming.csv | |
| https://www.nseindia.com/corporates/datafiles/CA_TODAY_SPLIT.csv | |
| https://www.nseindia.com/corporates/datafiles/CA_TODAY_BONUS.csv | |
| http://www.nseindia.com/corporates/datafiles/CA_LAST_1_MONTH_BONUS.csv | |
| https://www.nseindia.com/corporates/datafiles/CA_LAST_1_WEEK_SPLIT.csv | |
| https://www.nseindia.com/corporates/datafiles/CA_LAST_1_WEEK_BONUS.csv | |
| https://www.nseindia.com/corporates/datafiles/CA_MORE_THAN_24_MONTHS_SPLIT.csv | |
| https://www.nseindia.com/corporates/datafiles/CA_MORE_THAN_24_MONTHS_BONUS.csv | |
| http://www.nseindia.com/corporates/datafiles/CA_LAST_1_MONTH_RIGHTS.csv |
These are sample scripts in Python and Node.js for controlling the output format of the Gemini API using JSON schemas.
In a previous report, "Taming the Wild Output: Effective Control of Gemini API Response Formats with response_mime_type," I presented sample scripts created with Google Apps Script. Ref Following its publication, I received requests for sample scripts using Python and Node.js. This report addresses those requests by providing sample scripts in both languages.
| #include <stdio.h> | |
| #include <stdbool.h> | |
| #include <string.h> | |
| #define MAX_SIZE 100 | |
| struct Stack{ | |
| int top; | |
| char arr[MAX_SIZE]; | |
| } st; |
A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.
Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.
| /* Fonts */ | |
| /* Family */ | |
| h1 { | |
| font-family: 'Julius Sans One', sans-serif; | |
| } | |
| h2 { /* Contact, Skills, Education, About me, Work Experience */ | |
| font-family: 'Archivo Narrow', sans-serif; | |
| } |
| REM Windows Search | |
| sc config WSearch start=disabled | |
| REM SSDP Discovery | |
| sc config SSDPSRV start=disabled | |
| REM Geolocation Service | |
| sc config lfsvc start=disabled | |
| REM ActiveX Installer | |
| sc config AXInstSV start=disabled | |
| REM AllJoyn Router Service | |
| sc config AJRouter start=disabled |
| #!/usr/bin/env zsh | |
| git show-branch -a \ | |
| | grep '\*' \ | |
| | grep -v `git rev-parse --abbrev-ref HEAD` \ | |
| | head -n1 \ | |
| | sed 's/.*\[\(.*\)\].*/\1/' \ | |
| | sed 's/[\^~].*//' | |
| # How it works: |
| ; Fibonacci | |
| ; executable with https://schweigi.github.io/assembler-simulator/ | |
| ; Result is in register A | |
| JMP .start | |
| ; fib(n) <- n is in register A | |
| fib: | |
| CMP A, 1 ; compare n to a | |
| JE .fibReturnOne | |
| JB .fibReturnZero |
